Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] End Game Update

I don’t need the extra time – other than for documentation.  I think it would be good to get an idea on who needs the extra time to fix problems that they are already aware of.  Naturally, new problems will be reported as we continue testing the RCs.





From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Monday, May 08, 2006 9:55 AM
To: CDT General developers list.
Subject: [cdt-dev] End Game Update


After considering feedback from the conference call and looking at my own schedule, I’d like to propose the following changes to the 3.1 end game. I have to admit that picking the end of May for RC1 and making it the provisional last RC was somewhat arbitrary. I think the number of contributors to 3.1 is small enough that we can manage the end a bit tighter. As such, here’s another proposal.


RC0 – May 1 (done)

RC1 – May 15

RC2 – May 29

RC3 – June 12 (GA candidate)

RC4 – June 26 (only if necessary, emergency fixes only)


This will give us more formal bi-weekly releases to the community for testing. It also pushes the GA candidate out to June 12 and still gives us two weeks to ensure there are no more fixes needed.


Please comment. Does this push the envelope too far? Is this a more realistic schedule?


Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member



Back to the top