Re: [wtp-releng] WTP build from Git to sniff test

[Carl Anderson <ccc@xxxxxxxxxx>]

Konstantin,

There is a doc/wiki with step-by-step instructions for releasing code.  I am working through a release right now to finalize the initial version of that document, and will send out a link soon.  The platform releng tools do not work well for Git.
For now, we will continue with the map files.  The platform has set up tools to autotag map files for changes, and I would like to progress towards utilizing those same tools, but it should take about as long to get those tools running as it did to get the build from Git running, and we have to declare this week for both Kepler M1 and Juno SR1 RC1.  So for now, we will live with map files, and we can discuss it more in the future.
Also, as a note to all: I am doing the final work to branch the map files over to R3_4_maintenance for Juno SR1 work- please do not update the map files until I send a note stating that they are finished and ready for use.

FWIW,

- Carl Anderson

"Konstantin Komissarchik" ---08/14/2012 06:58:54 PM---Is there a doc/wiki with step-by-step instructions for releasing code (updating maps) in Git world?

From:	"Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
To:	"Webtools releng discussion list" <wtp-releng@xxxxxxxxxxx>
Date:	08/14/2012 06:58 PM
Subject:	Re: [wtp-releng] WTP build from Git to sniff test
Sent by:	wtp-releng-bounces@xxxxxxxxxxx

---

Is there a doc/wiki with step-by-step instructions for releasing code (updating maps) in Git world? Have platform releng tools been updated for Git?
 
While we are on this subject, has there been any consideration given to doing away with map files? The original motivation for maps no longer exists with Git as it is trivial for developers to collaborate on complex changes without contaminating branch tip with unfinished changes.
 
- Konstantin
 
 
From: Carl Anderson 
Sent: Tuesday, August 14, 2012 3:46 PM
To: Webtools releng discussion list 
Subject: [wtp-releng] WTP build from Git to sniff test

Folks,

We finally got a build of WTP from our Git repositories.  Please note that the map files are *NOT* ready for people to start releasing code... however, this build was done purely (as far as I can tell) from our Git repositories.  I offer it up for you to download and peruse, to ensure that the contents are similar to our WTP builds from CVS:

http://build.eclipse.org/webtools/committers/wtp4x-R3.5.0-I/20120814182035/I-3.5.0-20120814182035/

One big way to tell that we are using Git instead of CVS is the unexpected comparator log file- we have 365 instances of:
The manifest header "Eclipse-SourceReferences" has different values.
Which is exactly what I would expect, since the source reference now refers back to our Git repository, instead of CVS.  If anyone detects an issue with the contents of this build, please open a bug against releng, and notify this list.

Now, my plan of action from here:  The webtools.maps.git repository was fixed today!  As such, I now need to officially put all of the map file changes into that repository... then I will branch off R3_4_maintenance (for WTP 3.4.1), and then I will send out a note to this list letting people know that they can release code to both the master (for WTP 3.5.0) and R3_4_maintenance (for WTP 3.4.1) streams.  One more important note- when you tag a repository, please make sure that you push your tag up to the eclipse.org git repositories... otherwise, the build will not be able to find the tag that is placed in the map file!

If you have any questions/comments/concerns, please let me know.

Sincerely,

- Carl Anderson
WTP Build guy 

---

_______________________________________________
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