[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] CDT 4.0 Freeze Date
|
Er, oops, I confused my own dates... the 30th is the Monday not the Friday.
Yeah, build on the morning of Monday the 30th sounds right to me.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
From: Chris Recoskie/Toronto/IBM@IBMCA
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: 19/02/2007 02:23 PM
Subject RE: [cdt-dev] CDT 4.0 Freeze Date
:
I was thinking we'd allow checkins on the 30th and do the build after that
(Monday morning?). That way people have the weekend if the world blows up.
No one is going to be trying out a newly minted build on the weekend
anyway...
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
From: Doug Schaefer <DSchaefer@xxxxxxx>
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: 19/02/2007 11:19 AM
Subject RE: [cdt-dev] CDT 4.0 Freeze Date
:
Being realistic, we all know "Freeze" is a state of mind. If I want a
change
bad enough, I can make it look like a bug fix by holding it up to the light
in a certain way. ;)
I would like to make a serious judgment on what work we have left at the
May
conference call and start tossing features that aren't done yet. To do
that,
I would prefer to stick with the end of April as the official feature
freeze
date just to make sure we have it in our minds that after that we'd better
be slowing down or the train isn't going to make the stop.
Using the build from the morning of April 30 as some kind of official
feature frozen build, if you need such a thing, makes sense to me.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC Member
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Chris Recoskie
> Sent: Monday, February 19, 2007 11:02 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] CDT 4.0 Freeze Date
>
>
> Committers and contributors,
>
> I would like to clarify and solidify our feature freeze date for the 4.0
> release to make my life easier while I'm wearing my project management
> hat.
>
> On the last monthly project call we figured that the freeze would be
> between M6 and M7, or "around the end of April". Theoretically after
this
> date we would be restricted to bugfixing and there would be no more
> feature
> work or API changes happening. M7 (Friday, May 11) is the actual release
> which would have the frozen content, so in practice as developers our
> actual freeze would be shortly prior to this to allow for the build
> logistics to happen as well as to allow for a bit of ramp down.
>
> So the way I see it, the logical dates for our own internal freeze would
> either be Monday, April 30th, or Monday, May 7th. Given the churn going
> on right now I'd be inclined to shoot for the later date because last
> minute issues are bound to come up.
>
> Comments? Opinions?
>
> ===========================
>
> Chris Recoskie
> Team Lead, IBM CDT Team
> IBM Toronto
> http://www.eclipse.org/cdt
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
