[wtp-dev] Re: Fw: [wtp-committers] BUILD PROCESS & CALENDAR

[Craig Salter <csalter@xxxxxxxxxx>]

Hi Deniz,

I'm just curious to know how this compares
to the existing process the other eclipse teams use.   I'm assuming
that we should follow their development/build process unless there's a
good reason to do otherwise.   Internally, we've always developed
by manually tagging our own plugins and updating our maps when required
(typically using the release tool to do so).  We've never had a process
where files are automatically retagged on by some automated weekly process.
  So that's the bit them seems odd to me.  From eyeballing the
eclipse source's CVS history it seems that they tag in 'irregular' intervals,
which would suggest to me that there process is similar to the way we've
previously done things.

Is any one familiar with the process
the eclipse core team uses?

thanks

Craig


Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM 
Phone: (905) 413-3918  TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx     Notes: Craig Salter/Toronto/IBM@IBMCA

Deniz Secilir <deniz.secilir@xxxxxxxxxxxxx>

11/05/2004 01:14 AM

To	Craig Salter/Toronto/IBM@IBMCA
cc	wtp-committers@xxxxxxxxxxxxx, wtp-dev@xxxxxxxxxxx
Subject	Re: Fw: [wtp-committers] BUILD PROCESS & CALENDAR

Hi Craig,

I'm open to any improvements.

Thanks

Craig Salter wrote:

Hi Deniz, 

This process seems strange to me... but perhaps only because it is different
to what we've done in the past.  Is this the process the other eclipse
teams use? 

thanks

Craig


Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM 
Phone: (905) 413-3918  TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx
    Notes: Craig Salter/Toronto/IBM@IBMCA

Deniz Secilir <deniz.secilir@xxxxxxxxxxxxx>

11/03/2004 09:06 AM

To	wtp-committers@xxxxxxxxxxxxx, wtp-dev@xxxxxxxxxxx
cc
Subject	Re: Fw: [wtp-committers] BUILD PROCESS & CALENDAR

At 10:25 AM 11/3/2004, you wrote:

Hi Keith, 


We are re to adyadd some of our plugins to the WTP builds.  Can committers
update the script files in the org.eclipse.wtp.releng plugin as well? 
We have a dependency on GEF, so we need to update the scripts to extract
the GEF zip to the base location. 



The build scripts are now updated to download from
a URL. You can add your changes for GEF plugin ( provide URL for GEF Build
in build.cfg file and add script for downloading and unzipping).   
Or just send me the URL and I will do it for you.






Question regarding the following point in the Build Workflow for WTP where
you say "Label your code in CVS with the .map
files labels for the Monday integration build".  We're
unclear as to what this means.   Are these labels already in
place prior to tagging the source files?  When we commit/release a
change, the release tool should tag the source files and then update the
map file with the appropriate tag.  Does this step mean we have to
do additional tagging?  Can you provide a simple example to clarify?

Here is how the workflow goes:

-On monday, releng team labels wst and jst projects from HEAD on with the
tag for friday (i.e. v20041224 ), the milestone build ( WTP 1.0M2
).   The label is always the date preceeded
by a "v".  You do not have to anything for this.

-Developers decide which label goes to the build by editing their corresponding
plugin/feature in a .map file.  By default we will move them to the
current lane on Monday.  If anybody prefers a different label to be
used, we need to be notified.

>From this point on, committers will decide what will be gone for Friday's
milestone build by moving the label.   For the two integration
builds on monday and wednesday with the current label (v20041224). 

Committers are responsible for following these builds and solving build
problems by moving their labels. Release tool will not label any file.
It uses the release which is defined in map files.

  
Also, are the current *.map files final/set?  Should we split the
wst.map file into separate map files based on subcomponents?  I noticed
jdt has jdtcore.map, jdtdebug.map, jdtui.map files.



You can split map files on subcomponents. We use all *.map files in maps
folder so there is no problem in splitting them.



Thanks

Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com





-- 
Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com