Hi David,
Thank you for the guidelines. I will clarify in the bug what is the intended target branch.
I’ve increased the service level with +1 and released the change to build. This was done about 5 hours ago.
Greetings,
Kaloyan
From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: 13 май 2011 г. 10:10 ч.
To: Webtools releng discussion list
Subject: Re: [wtp-releng] Smoke Test Request for WTP 3.3.0 I-build for RC1
This is partially a guess, partially based on an IM discussion with Carl, who I think had a similar situation.
Apologies if I'm guessing wrong, but I think Kate Price contributed some improvements, and she intended to contribute to both maintenance and head. You can confirm with her, in bugzilla if there's doubt about that.
I think the best way to resolve the issue is to make HEAD (Indigo) stream correct, and increment service field by +1, to trivially avoid the trivial warning. And, release that for a a build ... RC1 if you are up already and have time "this morning".
Then, go back and create a branch of that head code info R3_2_maintenance ... same content ... same versions ... but do not release it right now ... since we are done with 3.2.4. But would be good to have head version correct and matching maintenance content, and then open a new bug open with 3.2.5 target, so as soon as we start building 3.2.5 we can release that bundle there, and then the bundles will be the same in both streams ... which I'm 99% sure is the intent. Once that is done the built bundles should have the same version and qualifier. This would be a case you would not need to do a full release in 3.2.5 (no need to retag in that branch) as long as you are sure the content is the same ... just use the same tag in the map file. That way, if there are future changes, they can be made to either stream with little trouble, and little risk of confusion at that later time.
Naturally ... I could easily be misunderstanding ... and others may have better ideas ... but those are my best guesses. Hope they help at least a little.
Thanks,
"Raev, Kaloyan" ---05/12/2011 02:41:51 PM---Hi, Regarding org.eclipse.jst.ejb.doc.user.
From: "Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
To: Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
Date: 05/12/2011 02:41 PM
Subject: Re: [wtp-releng] Smoke Test Request for WTP 3.3.0 I-build for RC1
Sent by: wtp-releng-bounces@xxxxxxxxxxx
Hi,
Regarding org.eclipse.jst.ejb.doc.user.
The released change is in relation with bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=337865.
However, this bug is not completely fixed. Somehow, I overlooked it – perhaps, because I did not triaged it to a specific milestone from the beginning.
Unfortunately, there are several issues:
· Only the patch in the doc is submitted, but the patch for the source code is not.
· The ejb.doc plugins has not been branched for 3.2 maintenance. So the patch in the documentation went in both 3.3 and 3.2 streams.
Any idea what is the best way to resolve from this condition?
Greetings,
Kaloyan
From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of NICHOLAS SANDONATO
Sent: 12 май 2011 г. 21:13 ч.
To: Webtools releng discussion list
Subject: Re: [wtp-releng] Smoke Test Request for WTP 3.3.0 I-build for RC1
I released changes for org.eclipse.wst.standard.schemas via Bug 345616.
From: | David M Williams/Raleigh/IBM@IBMUS |
To: | wtp-releng@xxxxxxxxxxx |
Date: | 05/12/2011 09:52 AM |
Subject: | [wtp-releng] Smoke Test Request for WTP 3.3.0 I-build for RC1 |
Sent by: | wtp-releng-bounces@xxxxxxxxxxx |
Smoke Test Request for WTP 3.3.0 I-build for RC1
Please document your Project's testing and approval of this build,
by 2 PM Thursday (Eastern Time) (at the latest),
or let us know if that's not possible.
We will need a respin, to get to "release candidate quality", but these should not effect smoke testing. This need to re-spin comes from a couple of "releng tests" failures, that should be fixed for an RC (effected teams can open your own bugs).
A. There is one "layout error":
1. Missing pattern or file: about.html in file: org.eclipse.jpt.jpadiagrameditor.doc.user_1.0.0.v201105070000.jar
B. And several "versioning errors":
Features with versioning errors
org.eclipse.jst.enterprise_userdoc.feature
3.3.10.v201103302046-62FUFBgJ9EA9ZGbJIGc (current)
3.3.10.v201104200444-62FSgBgJ9EA9YGdILLd (reference)
Bundles with qualifier-only increases
org.eclipse.jst.ejb.doc.user
1.1.300.v201103302046 (current)
1.1.300.v201103302045 (reference)
org.eclipse.jst.servlet.ui.infopop
1.0.400.v201103302035 (current)
1.0.400.v201103302034 (reference)
org.eclipse.wst.standard.schemas
1.0.301.v201103302014 (current)
1.0.301.v201103302013 (reference)
Features with qualifier-only increases
org.eclipse.wst.server_userdoc.feature
3.1.120.v201104182005-20DF7w312215222664 (current)
3.1.120.v201104182004-20DF7w312215222664 (reference)
Current Build
http://build.eclipse.org/webtools/committers/wtp-R3.3.0-I/20110512065202/I-3.3.0-20110512065202/
Smoketest Results
http://wiki.eclipse.org/WTP_Smoke_Test_Results_R330_05122011_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
