I vote to exclude test bundles from “qualifier only
increase” checks. It should be sufficient that version is newer than the previous
release. The careful consideration of the meaning of the version is wasted on test
bundles.
While I certainly agree that not having an exception for test
bundles is easier from the standpoint of this test, every time this test trips,
committer spend time resolving these issues. In my opinion the payoff for
resolving these issues on test bundles is not really worth the efforts
expended.
- Konstantin
From:
wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On
Behalf Of David M Williams
Sent: Thursday, January 28, 2010 9:18 AM
To: Webtools releng discussion list
Subject: RE: [wtp-releng] Smoke Test Request for WTP 3.2.0 S-build
>
why are these checks even covering test bundles?
I've
assumed the versioning rules we've agreed to cover all our delivered bundles.
And the test bundles a "deliverable". For example, their
license files need to be correct. Adopters can download them and run time.
Committers can provision them in their targets.
But
typically we have not held up declaring a build if that was the only problem.
The
purpose of these reports is to help us all catch "errors" early, that
otherwise might not be noticed for a while, thus making each milestone a little
closer to "release quality".
I
hope everyone finds them helpful.
I'm
open to suggestions, and the will of the committers as a group, it seems easier
to me just to make the bundles correctly follow the versioning rules, rather
than do the programming to make exceptions to the rule.
Thank
you for asking for that clarification. I'm sure others have/had the same
question.
|
From:
|
"Konstantin
Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
|
|
To:
|
"'Webtools
releng discussion list'" <wtp-releng@xxxxxxxxxxx>
|
|
Date:
|
01/28/2010
11:36 AM
|
|
Subject:
|
RE:
[wtp-releng] Smoke Test Request for WTP 3.2.0 S-build
|
|
Sent by:
|
wtp-releng-bounces@xxxxxxxxxxx
|
I
released changes to fix the version issue in the test bundle, but why are these
checks even covering test bundles?
-
Konstantin
From:
wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David
M Williams
Sent: Thursday, January 28, 2010 5:49 AM
To: wtp-releng@xxxxxxxxxxx
Subject: [wtp-releng] Smoke Test Request for WTP 3.2.0 S-build
Smoke Test Request for WTP 3.2.0 S-build
Please document your Project's testing and approval of build, by today,
Thursday, 2 PM (Eastern Time), or let us know if that's not possible.
I am a torn about making this request. Teams may want to wait until the next
build, but it won't be ready until after noon, and we will probably need
another build after that!
There are several issues:
There is another S-build already running this morning (started an hour ago, or
so, which means someone checked in a change after the deadline ... or at least
near midnight? and I do not know what change was checked in that kicked off
that build).
There are a number of Unit tests failures, spanning lots of function: xml, jsp,
jsf, jpa -- so lots of investigation and presumably some fixes need to be done.
In the last build, there's still one more "versioning error" that
would require a fix and respin to have a green build.
Bundles with qualifier-only increases
org.eclipse.wst.common.project.facet.core.tests
1.4.0.v201001141844 (current)
1.4.0.v200902182122 (reference)
So, I'll leave it up to each team. You may smoke test now, with the caveat that
you may decide to also smoke test the next build(s),
depending on what fixes are needed to clean up?
Please report to wtp-releng as teams investigate, and make plans to produce a
suitable milestone build.
Current Build
http://build.eclipse.org/webtools/committers/wtp-R3.2.0-S/20100128031257/S-3.2.0M5-20100128031257/
Smoketest Results
http://wiki.eclipse.org/WTP_Smoke_Test_Results_R320_01282010
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
