RE: [wtp-releng] Status of RC2 builds and schedule

["Konstantin Komissarchik" <kosta@xxxxxxx>]

Is it really already time for RC2 shutdown? We don’t even have a working RC1 build to my knowledge. Well, I did get confused by that and assumed we had more time. I do have one important bug fix that needs to get into RC2. It still needs final review and noon eastern time doesn’t give much time for us on the West Coast. I suggest that the deadline be moved to end of the day today. I don’t expect anyone to be running smoke tests in the middle of the night and the build should be ready by Friday morning.

 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=228568

 

- Konstantin

 

 

From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Thursday, May 22, 2008 4:58 AM
To: Webtools releng discussion list
Subject: [wtp-releng] Status of RC2 builds and schedule

 

I've been told it's not obvious, but yes, it is ok to check in your approved changes for RC2 now. (there is, or was, no reason for a re-build after all). [not to mention I discovered there had already been enough changes we would have had to have a branched build anyway].

So ... with that ... and other confusing factors this week ... I suggest we modify our schedule by "half a day" or so, as follows, since our schedule originally called for all RC2 code to be in by last night: (and, if any part of this does not make sense to you, or if you need other adjustments, just ask and we'll come up with something that does make sense for you (and your time zone :).

Let's get all approved RC2 code in by noon today (Eastern).
Build would then be ready by around 5 PM this evening (Eastern).
Smoke test, when asked, what ever build is ready then.
We'll continue to re-build as pre-reqs finish up.  
While we don't need to officially track more than one smoke test, per week, per team,
as we've seen, it's a good idea to sanity check every build!

We will still try and have an "internally declared" RC2 build on Friday, with official declaration next Tuesday.

Hope this makes sense, if not, let's discuss.
And, keep us all informed via this list if you need some other build, or urgent bug fixed.

Thanks,

Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.