[wtp-releng] Source Editing and JSDT branched for maintenance as R3_2_ma

[Nitin Dahyabhai <nitind@xxxxxxxxxx>]

Just to make sure there's no more confusion,
everything in the Source Editing and JSDT projects is now branched for
maintenance as R3_2_maintenance, map files as well as plug-ins & features.
 With 3.2.1 so tightly controlled and having its patch attachment
review process already in progress (we're in the project lead approval
stage, fyi), it was decided that we're better off clearing up HEAD for
3.3 and bigger changes sooner rather than later.  When releasing code,
double-check the comments in the map files to make sure you're in the right
branch.

Thanks all,
---
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational

From:	David M Williams/Raleigh/IBM@IBMUS
To:	Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
Date:	06/22/2010 09:05 PM
Subject:	Re: [wtp-releng] New build and development streams are open for        business
Sent by:	wtp-releng-bounces@xxxxxxxxxxx

---

Correction ... Nitin has reminded me that due to JSDT's history, the code
already has branches in the "3.x" range, so ... 
even though its features are at "1.x" range,  the code,
and map files will be branched as R3_2_maintenance (instead of R1_2_maintenance
as stated in original note). 

Nitin has done the branch of the map files, and I will update the build
files this evening to use the R3_2_maintenance maps.

From:	David M Williams/Raleigh/IBM@IBMUS
To:	wtp-releng@xxxxxxxxxxx
Date:	06/17/2010 03:36 AM
Subject:	[wtp-releng] New build and development streams are open for business
Sent by:	wtp-releng-bounces@xxxxxxxxxxx

---

I have set up new builds for WTP 3.2.1 and WTP 3.3.0.

WTP 3.3.0 is represented by the HEAD of the map files, and 
WTP 3.2.1 has branched map files, as described below. 

I looked for our previous write-up of how/when to actual branch your code
... 
in contrast to the maps which always have to be branched for maintenance
... 
but, I could not find it on our wiki. Let us know if any of you know where
it is. 

In brief, while you are doing ONLY maintenance (so maintenance and "next
major release" 
are the same code) you can develop in only HEAD, but just be sure to release
to the branched map files. 
You can often "compare" or merge branched map files with HEAD,
so they have the exact same version tags 
in both map files ... there is not really a need to "release"
twice. 
 
And then ... once maintenance and "next major release" code streams
start to differ, we have agreed in the 
past that code in the same map file, should all be branched together, at
the same time, and comments in the map file updated. 
This makes it easier for others to "load up" an environment for
what ever stream they are working on, 
where as if done bundle by bundle, no one can easily figure that out what's
what. 
[suggestions are welcome ... especially if you write it up on our wiki
:) 

Let us know if any issues or errors in the branching or build results.

Thanks, 

= = = = = = = 

WTP 3.2.1 map files branched 


JSDT 
R1_2_maintenance 
releng.jsdt 


Dali 
R2_3_maintenance 
releng.dali 


Others 
R3_2_maintenance 
releng 
releng.common 
releng.ejbtools 
releng.jeetools 
releng.jst 
releng.servertools 
releng.sourceediting 
releng.webservices 

_______________________________________________
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