Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Opt-in process

Given the compressed timelines, along with the assumption that the subset of projects that will participate in each iteration will be smaller that the usual "big bang" in June, I'm going to change how we determine dates for things like CQ, and IP Log deadlines, and timing of release reviews.

Here's what I propose:

The CQ submission deadline for third-party dependencies will be at the end of Week 1 of the 13 week release cycle. The IP Team will, naturally, do their best to accommodate exceptions. 

Project teams that are contributing new content (i.e. a major, minor, or service release) should create a release record before the end of week 3. This is, effectively, the opt-in deadline for any particular cycle. We have some related bugs open regarding how we declare and track participation; addressing these needs to be part of a larger discussion of what we're tracking and why. Note that the IP Team has started using the dates on release records as part of their planning/prioritization; specifying release dates early really helps with this.

We'll time the Release Reviews (for major and minor releases; reviews are not required for service releases) to use the slot that's closest to the actual release date. Reviews are run on the first and third Wednesdays of the month (which is the same as the GA date in the 2018-09 iteration).  IP Logs will be due two week ahead of this.

I will periodically run a scan of the aggregate repository to ensure that all of the third party content there has been properly vetted by the IP Team and raise a flag as early as possible when I detect something. This should, hopefully, avoid surprises at release time.

Voice your concerns soon, please.


On Wed, Jul 11, 2018 at 3:38 AM, Mélanie Bats <melanie.bats@xxxxxxx> wrote:

During the call yesterday, the opt-in process was discussed.

The opt-in process is still not clear for everyone. It was written on the FAQ[1] : "The period to join the simultaneous release is at the beginning of any cycle, four times a year. The project needs to declare its intention to join before the +0 (Friday) of the M1 release week. The "statement of intent" is still exactly the same as today: projects must formally announce their participation on the cross-projects-issues-dev mailing list.
Once a year, EMO will take care of organizing the “opt-in” process as it is today, so that all projects already in the train can declare their intention to continue. Those not opting to continue will be removed, but can be re-added should their intention change."

This means that projects should opt-in before July 13th for the 2018-09 release.

We agreed during the call that the opt-in will occur once a year after the June release and means that project will be in for a year.

If it is ok, I will clarify the situation on the FAQ and on cross-project.

Best regards,

Mélanie Bats
+33 7 87 69 42 84
+33 5 34 57 16 29

25 Boulevard Victor Hugo - Colomiers - France
_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top