I think this is a good idea, this time.
So looks like there will be another S-build that only JSF will smoke test
... probably won't be finished until approx 9 PM Easter ... so we'll promote,
hopefully, late tonight or Saturday.
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
09/26/2008 12:45 PM
RE: [wtp-releng] Status of 3.1 M2?
Sorry, I didn’t release some
of the changes in 3.0.2 to 3.1 for the JSF project.. I would like to fix
this and re-spin the M2 build. This should not affect the smoke test results
of other subprojects.
From: David M Williams [mailto:david_williams@xxxxxxxxxx]
Sent: Thursday, September 25, 2008 8:41 PM
Subject: [wtp-releng] Status of 3.1 M2?
Well, the JUnit numbers did better (though maybe because of a Did-Not-Finish
for some suites ... that's usually caused from a hang, though can be from
unexpectedly long tests ... I think our limit is currently 2 hours per
suite ... 4 hours total).
But, I have another concern.
According to the "versioning report" there are 8 bundles where
the 3.0.2 _service_ has not been put into our 3.1 (HEAD) branch yet.
If it is not obvious, this part of the versioning report is not about some
technical rules we should follow, but indicates our 3.1 builds will perform
"worse" than our 3.02 builds
(at least for what ever bugs were fixed in 3.0.2).
What's up with that? Even if we are "on time" I don't think we
have accomplished "predictable deliveries".
What shall we say when we announce M2? That is. how should we phrase this
to the Eclipse community of (early) users and adopters?
Will the Project Leads of these following bundles (or component owners)
please suggest appropriate wording?
(I have not included, in this list documentation bundles nor test bundles,
nor bundles that have "qualifier only"
increases ... which at least means extra code and not missing code !