[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] [technology-pmc] Fwd: [eclipse.org-planning-council] Luna participation
|
> To join a Simultaneous Release, Projects must have stated their intent to do so by M4, at the latest. The "statement of intent" is done by formally announcing participation on the cross-projects-issues-dev mailing list (EMO will update the Luna participation page). Projects are expected to have a release record completed that includes (at least tentative) plan information prior to announcing their intent to participate. The announcement must include the name of the project, a link to the release record, and the offset (+0, +1, …)
Code Recommenders will join the release with a 2.x version.
The project plan for 2.0 is available here [1].
Our offset is +3 as we depend on a couple of projects (xtext, xtend, jgit, m2e) and have no known dependents.
Thanks,
Marcel
[1] http://projects.eclipse.org/projects/technology.recommenders/releases/2.0.0/plan
On Sep 9, 2013, at 4:53 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
> FYI: If you are a Technology project and plan to participate in Luna please make sure to read through the following email as well as subscribe to the cross-project-issues-dev@xxxxxxxxxxx mailing list (if not already done so).
>
> Thanks!
>
> -Gunnar
>
> Anfang der weitergeleiteten Nachricht:
>>
>> Dani
>>
>>
>> From: Wayne Beaton <wayne@xxxxxxxxxxx>
>> To: eclipse.org-planning-council@xxxxxxxxxxx
>> Date: 29.08.2013 05:03
>> Subject: [eclipse.org-planning-council] Luna participation
>> Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
>>
>>
>>
>> Greetings Planning Council.
>>
>> With Kepler, I populated the "participating projects" page [1] in the PMI based on the contents of the portal. As projects showed up late, I updated the page manually.
>>
>> I've created a page for Luna [2] and have updated the process in the documentation [3].
>>
>> The short version is that I've turned things around with the new implementation. In the old implementation, a project had to "flip the bit" in their own project metadata via the portal. This was pretty difficult to track as there was no notification when a change occurred, and there was no restriction on when the bit could be flipped. Several projects added themselves retroactively to one or more releases.
>>
>> The current implementation starts from the Simultaneous Release record. To that record, I can add a project, version, and offset. My intention is open this functionality up to Planning Council members, but I haven't got that implemented yet. In the meantime, it has to be me that makes the change.
>>
>> I will monitor the cross-project-issues-dev mailing list and update the record as declarations of participation come in. I'll look to the top-level project representatives on the Planning Council to make sure that no projects are forgotten (i.e. tell me if you notice a discrepancy). Making projects use the mailing list has the benefit of ensuring that they're actually on the mailing list. It has the further advantage of giving me an opportunity to press projects to create a release record and populate it with plan information. Again, I look to the top-level project representatives to assist with this.
>>
>> There is likely going to be some confusion, especially for projects that have been participating for a while. I will make an announcement on the cross-project-issues-dev mailing list describing the change in process.
>>
>> Wayne
>>
>> [1] https://projects.eclipse.org/releases/kepler
>> [2] https://projects.eclipse.org/releases/luna
>> [3] http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
>> --
>> Wayne Beaton
>> Director of Open Source Projects, The Eclipse Foundation
>> Learn about Eclipse Projects
>> [attachment "attm1uit.htm" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>>
>> 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.
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> --
> Gunnar Wagenknecht
> gunnar@xxxxxxxxxxxxxxx
>
>
>
>
>
> _______________________________________________
> technology-pmc mailing list
> technology-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/technology-pmc
