Community
Participate
Working Groups
At the recent planning council meeting, http://wiki.eclipse.org/Planning_Council/November_23_2011 it was concluded there were not resources to correct the "tracking data input" fields that is currently managed by the Portal ... hence, it should be "disconnected" and no longer displayed for Project leads, to avoid confusion. The field for "simultaneiousrelease" participation should still stay, of course, and its summary page at http://eclipse.org/juno/planning/SimultaneousReleaseOverview.php will stay. I will "remove" other summary pages at www.eclipse.org (I'll leave "deprecated" message there, in case the URLs are already in use from elsewhere) but will leave up to others to handle portal end of things. One issue, I do not know how to resolve, is that currently, projects can mark, with tracker, if they are "consolidating" their release documentation, IP logs, etc., with "tracker" data, and that hierarchy does show up in the "participation summary" page, at http://eclipse.org/juno/planning/SimultaneousReleaseOverview.php It seems it'd make it easier for EMO staff if that relationship was still tracked .... but, up to them on if or how to accomplish.
Ok, I've done my part, on "summary" web pages ... that is, removing all of them for Juno, except for http://eclipse.org/juno/planning/SimultaneousReleaseOverview.php and "disconnecting" it from other report links. I have removed no longer used files, but, for long term reference, I did tag the old pre-change versions with an obvious tag, v20111205_predisconnectbug365629, in case anything in them needs to be recovered. Over to you .... Wayne? to make changes on Portal end. I'd suggest if you can leave the one field "track with parent" (if you can) that would be useful information to help your book keeping at the end ... but, up to you.
I removed the tracker from the portal a couple of weeks ago, in favour of replacement functionality in the PMI. For the time-being, the functionality provided by the release tracker doesn't have a general interface; I have some open questions regarding how this should manifest. In my mind, for example, it doesn't make sense to allow any project at any time to declare that they're part of the release (including past releases as is supported by the old stuff). I am thinking that members of the planning council should be able to add projects to a simultaneous release. For now, however, that functionality is restricted to me. I have opened bug 402190 to track this. Specific releases can be associated with the simultaneous release. A project can opt to include zero or more subprojects in their release. So if a subproject is participating with their parent, they should be included in their parent's corresponding release record. Clearly, this will require some additional documentation. I'll work through the Web Tools project as as example of a "roll up" release and capture the workflow in the wiki.
