Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] RC2 produced - please be available this week for any final change requests

Per David’s note below, RC2 is ready. If problems are detected during the week, we’ll discuss (and vote on) them via email.


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Friday, July 22, 2005 7:15 AM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] RC2 Ready and auto builds turned off


Following a brief sanity check to confirm this build,

I20050722  Fri, 22 Jul 2005 -- 14:29 (-0400) ,

is anticipated to be promoted later today to official RC2 status.

This means auto build on cruise control has been turned off.

This means no more code changes without PMC approval.

Note: after RC2 is copied and promoted, you may notice some
"build activity" from time to time, but this will be to only fix some
JUnit scripts and (hopefully) to make some changes related to
"documentation builds". There will be no code changes, without
PMC approval and a notice being posted here on wtp-dev.

As for procedure, if components leads have a well tested, well reviewed, "fix in hand" and
want to propose it be released to a build for 0.7, please post a brief note
to wtp-pmc@xxxxxxxxxxx (with a link to the bug -- the bugzilla entry itself should have
the details of the bug, the fix, the review, the tests, and some benefit/risk assessment).

Once this request posted to wtp-pmc@xxxxxxxxxxx, the PMC will communicate via phone,
email, or IM, to see if there is general agreement to include the fix and assume the
risk of changing the code this near release. (expect a turn
around time of from 8 to 24 hours).

If it is decided to include a change, a note will be posted here on wtp-dev that
the code is changing listing the bug numbers) and anticipated time of the build..

So ... enjoy your testing! And, remember, a well understood build with
known, well documented problems (with workarounds, if known) is better
at this point -- and still a noble pursuit -- than fixing a few small bugs and risk
introducing worse or unknown bugs.

wtp-dev mailing list

Back to the top