| Re: [eclipse.org-planning-council] Excpetion request to allow Riena to join the Helios train late. |
I have done my TODO from yesterday's meeting. This is a formal request to start the exception process to allow Riena to join the Helios train late (after M4). Using the process documented at http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php#pcExceptionProcess I have already gotten approval from the RT PMC to make the exception request on behalf of the Riena project. See http://dev.eclipse.org/mhonarc/lists/rt-pmc/msg01117.html
I am requesting a vote by other active planning council members to approve of this exception for late participation. The Riena project wants to participate in the Helios release.
As a planning council member my vote is +1 (two more needed to approve the exception)
Here is an explanation provided by the project team (Christian Campo) for the lateness and the justification of why Riena should be allowed to join:
--------------------------------
yes that is an oversight and someone (thats me) is working on getting it done.
I guess the reason that I missed M4 is first that I read somewhere that since Riena was in Galileo that Riena will be automatically in Helios. The oversight was that I must provide a Riena version for M4 build in order to be on the train and not just communicate the interest of the project. Very Sorry for that.
At the time Helios M4 was we were busy creating the Riena 1.2.0 release (based on Eclipse 3.5) since we are currently on a bi-yearly release circle (Releases in June and December) for Riena. (to get more features into the hand of users)
Yes please I want to be on the Helios release train. We have our release plan ready aligned with Helios http://www.eclipse.org/projects/project-plan.php?projectid=rt.riena and we are currently in the process to get the build working based on Eclipse 3.6 milestones since we had it always in our mind to be part of Helios.
For the justification part (why is it important) we have quite a number of people that I know that are running projects based on Riena and consume it through p2 update sites or the Galileo repository. We have other open source projects like redView (Ekke Gentz who is also Riena committer) which are basing their work on top of Riena milestones. And we could feel the difference once Riena was in the repository (in Galileo) the first time that more people would give it a shot since they were interested in the topic that Riena is covering and updating from a global repository lowers the barrier to try it.
Anything more I need to provide or need to do, please let me know.
Very sorry that I am creating this extra effort for you.
thanks
christian
-----------------------------------
David M Williams---01/07/2010 01:58:36 AM---Did I mention there'd be a quiz? :)
From:
David M Williams/Raleigh/IBM@IBMUS
To:
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date:
01/07/2010 01:58 AM
Subject:
[eclipse.org-planning-council] Who got the most "to do" items at today's meeting?
Did I mention there'd be a quiz? :)
http://wiki.eclipse.org/Planning_Council/January_06_2010
I thought it would be prudent to remind those of you with "to do" items that some of them need to get done in the next week or two.
As always, if something is unclear ... just ask.
Thanks, _______________________________________________
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.
_______________________________________________
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.
