Re: [eclipse-pmc] Galileo SR1 endgame

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

> Perhaps we
could add a PMC +1 for fixes during RC3 and RC4.

We already have this, in the process
copied from previous maintenance releases (although this was previously
RC2/RC3). After re-reading the freeze plan the current approvals actually
seem reasonable (component lead approval up to RC2, and PMC approval for
RC3+). Perhaps the retrospective comment was aimed at more careful control
during the general maintenance release cycle, rather than the end-game
in particular.

John

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

08/05/2009 03:26 PM

Please respond to
eclipse-pmc@xxxxxxxxxxx

To	eclipse-pmc@xxxxxxxxxxx
cc
Subject	Re: [eclipse-pmc] Galileo SR1 endgame

This makes sense to me. We should send a note to eclipse-dev
and equinox-dev today to inform them about this Friday's 3.5.1 build for
RC1.

I think the rules of engagement for fix approvals should be the following:

Another committer and the component lead must +1 the bug report. All changes
must have their associated bug reports tagged 3.5.1. (Ongoing changes to
component documentation do not require special approval.)

Perhaps we could add a PMC +1 for fixes during RC3 and RC4.

Tom

John
Arthorne ---08/05/2009 01:54:35 PM---At today's planning council call,
the dates for Galileo SR1 were finalized [1]. The only notable change from
previous years is

From:	John Arthorne <John_Arthorne@xxxxxxxxxx>
To:	eclipse-pmc@xxxxxxxxxxx
Date:	08/05/2009 01:54 PM
Subject:	[eclipse-pmc] Galileo SR1 endgame

---

At today's planning council call, the dates for Galileo SR1 were finalized
[1]. The only notable change from previous years is an *extra* release
candidate three weeks earlier on August 10-14th. This was based on the
experience last year where there were problems getting the release train
builds started that resulted in a very late RC1 build. Contribution to
this first build is optional. Based on these dates I have created a draft
Galileo SR1 endgame plan [2]. This plan is based on the Ganymede SR1 plan,
with RC1,RC2,RC3 renamed to RC2,RC3,RC4, with the new RC1 inserted at the
beginning. Please send any comments on this draft plan, especially in light
of the retrospective suggestion to introduce more control into the maintenance
release process. I haven't added any extra process into this draft, but
I'm awaiting your input on whether we should make changes.

Note this schedule requires our RC1 build to be *this* Friday, which is
very short notice. I suggest we let everyone know about this, but finalize
and publish the end-game plan next week after discussing it next Wednesday.

John 

[1] http://wiki.eclipse.org/Galileo_Simultaneous_Release#SR1
[2] http://www.eclipse.org/eclipse/development/plans/freeze_plan_3_5_1.php_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc