Re: [eclipse-pmc] Galileo SR1 endgame

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipse-pmc] Galileo SR1 endgame

From: John Arthorne <John_Arthorne@xxxxxxxxxx>
Date: Tue, 11 Aug 2009 11:49:22 -0400
Delivered-to: eclipse-pmc@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipse-pmc>
List-help: <mailto:eclipse-pmc-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-pmc>, <mailto:eclipse-pmc-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-pmc>, <mailto:eclipse-pmc-request@eclipse.org?subject=unsubscribe>

These rules sound quite reasonable to me. I have updated the draft freeze plan with this information. We can finalize the decision at tomorrow's call.

John

Daniel Megert <daniel_megert@xxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

08/06/2009 02:47 AM

Please respond to
eclipse-pmc@xxxxxxxxxxx

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

>Perhaps the retrospective comment was aimed at more careful control during the general maintenance release cycle, rather than the end-game in particular. Right, the retrospective action doesn't speak about the end game in particular but about the maintenance build in general. I consider the maintenance release as something like 3.5 RC5, RC7 etc. but currently anyone can put in anything without any restriction (not even a peer review is requested) up until shortly before we ship the build (end-game start). I would install the following rules: Up to RC2 and including: +1 from component lead in the bug report plus an additional committer (can be the same as the component lead if he's not the one who made the fix) reviewing the code and setting 'review+' on the patch in the bug report. > RC2: +1 from PMC member in the bug report plus an additional committer (can be the same as the component lead if he's not the one who made the fix) reviewing the code and setting 'review+' on the patch in the bug report. And just to make it clear, I'd also add this: API change approval: No API changes are expected. Any exception must be approved by the PMC. No changes are to be released without prior approval and associated bug report. Send the request for approval to the eclipse pmc mailing list. If a change is made to API to make it binary compatible with 3.4, technically this is still an API change, and thus it should be treated in the same way as any other API change requests. Dani |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |John Arthorne <John_Arthorne@xxxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |eclipse-pmc@xxxxxxxxxxx | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |05.08.2009 22:27 | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [eclipse-pmc] Galileo SR1 endgame | >--------------------------------------------------------------------------------------------------------------------------------------------------| > 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 To eclipse-pmc@eclipse.o rg 08/05/2009 03:26 PM cc Subject Please respond to Re: [eclipse-pmc] eclipse-pmc@xxxxxxxxxxx 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 [attachment "atttqh1b.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "attys7kt.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "att1m0xd.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "attv5rf4.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "attw9m81.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "atteij1w.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "attsohn9.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "att0blfv.gif" deleted by Daniel Megert/Zurich/IBM] [attachment "attprtm5.gif" deleted by Daniel Megert/Zurich/IBM] _______________________________________________ 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

References:
- Re: [eclipse-pmc] Galileo SR1 endgame
  - From: Daniel Megert

Prev by Date: [eclipse-pmc] [CQ 3480] JUnit Version: 4.7
Next by Date: [eclipse-pmc] Re: B3 proposal
Previous by thread: Re: [eclipse-pmc] Galileo SR1 endgame
Next by thread: [eclipse-pmc] Bugzilla Target Milestones for 3.7
Index(es):
- Date
- Thread

Breadcrumbs