On 09/09/2013 10:03 AM, Daniel Megert
The Eclipse top-level
and offset 0.
Greetings Planning Council.
With Kepler, I populated the "participating projects" page 
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  and have updated the process in
The short version is that I've turned things around with the new
In the old implementation, a project had to "flip the bit" in
their own project metadata via the portal. This was pretty
track as there was no notification when a change occurred, and
no restriction on when the bit could be flipped. Several
themselves retroactively to one or more releases.
The current implementation starts from the Simultaneous Release
To that record, I can add a project, version, and offset. My
is open this functionality up to Planning Council members, but I
got that implemented yet. In the meantime, it has to be me that
I will monitor the cross-project-issues-dev mailing list and
record as declarations of participation come in. I'll look to
project representatives on the Planning Council to make sure
that no projects
are forgotten (i.e. tell me if you notice a discrepancy). Making
use the mailing list has the benefit of ensuring that they're
on the mailing list. It has the further advantage of giving me
to press projects to create a release record and populate it
information. Again, I look to the top-level project
assist with this.
There is likely going to be some confusion, especially for
have been participating for a while. I will make an announcement
cross-project-issues-dev mailing list describing the change in
Director of Open Source Projects, The
Learn about Eclipse
"attm1uit.htm" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
eclipse.org-planning-council mailing list
IMPORTANT: Membership in this list is generated by processes
the Eclipse Foundation. To be permanently removed from this
you must contact emo@xxxxxxxxxxx to request removal.