Hi David,
It was an accident. We are getting ready
to refactor and wanted a ‘release’ of the current code line to set
the baseline.
We will review the errors. And in future
will post a note to releng and be aware of the policy.
Thanks
Raghu
From:
wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Thursday, November 02, 2006
11:17 PM
To: wtp-releng
Subject: [wtp-releng] Reminder of
our no-release-for-build policy duringsmoky periods
It appears the JSF team released a bunch of changes
tonight, that caused another I-build to start up. (which has 8 compile errors,
btw).
So,
was this to fix some blocking defects? Or really bad regressions? Those are
normally the only reasons to get a new build, after we have asked everyone
to
smoke test a build.
If
they were for blocking defects, that's fine. A note here to wtp-releng is
always helpful though, to keep everyone up-to-date.
The
importance of this rule is that if some other team found a blocking defect we
need to know that we can quickly re-build with _only_ that one fix.
If
this was an accident, and you were really just getting started on next week's
code, that's fine, and there is no need to back out the changes this time.
But,
you will need to let us know which is the case, since we can't really decide
which I-build is our target this week until you do let us know.
Thanks,