Skip to main content

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


I'm sorry if this was discussed on the call. Previously the statement of intent had to include a link to the release record. If the statement now covers a whole year's worth of releases, are projects supposed to provide links to 4 release records? Or should the FAQ be clarified to say that the statement of intent doesn't need to provide a release record?


Sam Davis
Senior Software Engineer, Tasktop
Committer, Eclipse Mylyn

On Wed, Jul 11, 2018 at 12: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.

Back to the top