Re: [wtp-releng] Ready for 3.0.2 stream?

[Carl Anderson <ccc@xxxxxxxxxx>]

David,

      So, what you are saying here is that all of the components should tag
their R3_0_maintenance contents with R3_0_1 by 3 pm EDT today?  (If I
recall correctly, it is now the duty of each component to tag the contents
of their plugins... and that is something that should be done before 3.0.2
work begins.)

FWIW,

- Carl Anderson
WTP programmer


                                                                           
             David Williams                                                
             <david_williams@l                                             
             inux.vnet.ibm.com                                          To 
             >                         wtp-releng@xxxxxxxxxxx              
             Sent by:                                                   cc 
             wtp-releng-bounce                                             
             s@xxxxxxxxxxx                                         Subject 
                                       [wtp-releng] Ready for 3.0.2        
                                       stream?                             
             08/20/2008 09:24                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
              Webtools releng                                              
              discussion list                                              
             <wtp-releng@eclip                                             
                  se.org>                                                  
                                                                           
                                                                           




Some developers have asked me (well, ok, just one so far, but suspect
others would take advantage of it ... )
if they can start checking in 3.0.2 fixes into the R3_0_maintenance
branch ... and maybe even start the 3.0.2 M builds.

Normally, I'd say no, let's be cautious in case we have to re-spin
3.0.1. But, I think we've tested the breath out of 3.0.1 and a new stop
ship bug is very unlikely at this point. Plus, since we delayed 3.0.1,
we cut into the 3.0.2 cycle, so this would help to minimize the impact
of that reduced time .. giving a couple of days back to it.

So, if there's no objections by, say, 3 PM this Wednesday afternoon
(Eastern time) let's say 3.0.2 is open for business at that time.

In theory, after that point, we could still re-spin a 3.0.1 if required,
but since we don't often branch a previous version, it'd be a bit
riskier to do cleanly. Let me know if anyone thinks this too aggressive
or risky, but if no objection by 3 PM (Eastern) let's say it's ok for
those developers who are are going on vacation :) to commit and release
their 3.0.2 fixes.

If I have time, I may try to get the 3.0.2 builds started, but we won't
have any formal smoke test of 3.0.2 this week ... AND I do encourage
everyone to finish their 3.0.1 testing and verification of closed bugs
(especially those that were blocking or critical) by Thursday's status
meeting -- that still has top priority and this early 3.0.2 work is
definitely special case.

Thanks,

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