RE: [cdt-dev] Call for Status on I200606120500 as RC3

So far the score is nil-nil. Kinda like watching a World Cup game. L

I’ll vote go. I’ve been using it on some real projects and things look reasonably O.K. There have been a couple of exceptions reported so an RC4 is looking more likely but I’d like to get RC3 out for more testing in the community.

Either way, please vote.

Thanks,

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member

http://cdtdoug.blogspot.com

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Monday, June 12, 2006 9:47 AM
To: CDT General developers list.
Subject: [cdt-dev] Call for Status on I200606120500 as RC3

Hey gang,

The time has rolled around again for another RC call. We’ve made some great progress and the bug count is now sitting at 3. Thanks to everyone for their hard work in making sure we have a great quality CDT 3.1.

Please submit your go/no-go. I’ll tally the results tomorrow morning and if we’re good to go I’ll announce this build as RC3. If not, we’ll respin and try again.

Just a reminder that our process now shifts to critical but safe fixes only for the next two weeks. If we find that there are significant fixes going in, I’d like us to consider an RC4 next Monday, just to make sure we test for regressions.

Here is the list I have. Note that mine isn’t a code change:

129782	Chris Recoskie	Andrew Ferguson	ASSI	3.1	GnuMakefileGenerator can generate invalid makefiles via o...
142268	Doug Schaefer	Lawrence Mandel	NEW	3.1	CDT zips must include epl_v10.html and notice.html

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member

http://cdtdoug.blogspot.com