RE: [wtp-releng] Please smoke test WTP 2.0 I-I200611300401 by Friday

[David M Williams <david_williams@xxxxxxxxxx>]

Yes, map file changes committed to "head"
are the "trigger" for the build. For 2.0 I-builds, that is. This
applies to 
releng
releng-jsf, and 
releng.dali 

I actual fact, jsf and dali were just
added this week :) 
So, if you in jsf and dali release a
map file and do not see a build start within an hour or so, let me know
as it might be a bug in the new script. 
Or, if you're in a hurry :) post a note
here and I can "manually" start a new build. 

So when we say "release code",
we usually mean commit the code itself to head, and then use the "release
tool" (Tools --> Release) which 
   tags the project with the
new version you specify (vdatetime)
  updates the map file with the
the tag
  committs the map file to head



FYI, everyone should have this bookmark,
so that can check on current status of the builds: 
http://build.eclipse.org:7777/cruisecontrol/

"paused"  means only
built manually. 
"waiting" means waiting to
check for modifications .. which, not shown there, is 
        once
an hour for the most active streams, but 1 year :) for the old streams
        (that
is, effectively only built manually). 
"checking for modifcations"
 means .. as it sounds
"building" ... that's the
one that tells you all is well and a build should be ready within two hours

"raghunathan srinivasan" <raghunathan.srinivasan@xxxxxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

11/30/2006 03:13 PM

Please respond to
"raghunathan.srinivasan@xxxxxxxxxx"        <raghunathan.srinivasan@xxxxxxxxxx>; Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	"Webtools releng discussion list" <wtp-releng@xxxxxxxxxxx>
cc
Subject	RE: [wtp-releng] Please smoke test WTP 2.0 I-I200611300401 by Friday

Hi,
 
We have fixed the problem.
Is the following the process to release it?
 
1)
      Tag
the project that is fixed with a new version. Say, v20061130
2)
      Update
the map file for that project only
 
-Raghu

---

From: wtp-releng-bounces@xxxxxxxxxxx
[mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of RAGHUNATHAN
SRINIVASAN
Sent: Thursday, November 30, 2006 9:41 AM
To: wtp-releng@xxxxxxxxxxx
Subject: RE: [wtp-releng] Please smoke test WTP 2.0 I-I200611300401
by Friday
 
 Hi,

We are investigating the cause of the Junit failures in JSF and will post
status later in the day.
-Raghu

---

From John Lanuti <jlanuti@xxxxxxxxxx>
Sent Thu 11/30/2006 6:53
AM
To wtp-releng@xxxxxxxxxxx
Subject [wtp-releng] Please
smoke test WTP 2.0 I-I200611300401 by Friday
 

http://download.eclipse.org/webtools/committers/drops/R2.0/I-I200611300401-200611300401/

Please report status back by noon (EST) on Friday.

FYI - There are 34 failing Junits, but should not affect the masses.  JSF
and JPA please look into resolving these errors.

Thanks, 

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861

---

_______________________________________________

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