Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] heads up: 106036


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Doug Schaefer
> Sent: Thursday, August 04, 2005 10:36 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] heads up: 106036
> 
> Recoskie, Chris wrote:
> 
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=106036
> >
> > We might ask for a rebuild for this today... rather than waste time
> > doing multiple rebuilds it would probably be good to delay the rebuild
> > until we decide whether this is going into 3.0. I hope we will close
> > on that by the afternoon.
> >
> 
> O.K. I am still in a holding pattern. You know this is really pointing
> at the need to extend, or at least enforce, the release candidate cycle.
> We are getting some great testing that we really needed earlier in the
> cycle if there wasn't so much coding going on ;-) .
> 

Yes, but it is always like that 8-).  When we make a release candidate
available folks give it a go which result in lots of PR and adjustments
during the following weeks.  Folks are more interested in the RC and the
milestone since they feel the can safely use it instead of the unstable
nightly builds.  This behavior brings annoying side effects at the end of
the release cycle.

My motto now is ... serenity now and finding a happy place 8-)


Back to the top