View source for EPP/Obsolete/Galileo Packages/Release Actions

{{warning|Note: The contents of this page is obsolete, but it may still contain some interesting tid-bits.}}

[[Category:EPP:Obsolete]]

== Directories used in the description ==

* EPP_BuildDirectory = server <tt>build.eclipse.org</tt>, directory <tt>/shared/technology/epp</tt>
* EPP_DownloadDirectory = <tt>/home/data/httpd/download.eclipse.org/technology/epp</tt>

== Before the release ==

* Check that all package maintainers signed off on the wiki page: [[EPP/Galileo_Packages/Sign_Off]]
* Copy the p2 repository from build to download; usually it is created on <tt>build.eclipse.org</tt> in <tt>EPP_BuildDirectory/epp_repo/galileo/epp.build/buildresult/org.eclipse.epp.allpackages.feature_1.2.0-eclipse.feature/site.p2/</tt> and needs to be copied to a milestone subdirectory below <tt>EPP_DownloadDirectory/packages/galileo/</tt>
* Update <tt>compositeArtifacts.jar</tt> and <tt>compositeContent.jar</tt>

Structure of the composite p2 repositories in <tt>EPP_DownloadDirectory/packages/galileo</tt>:

<code><pre>
compositeArtifacts.jar        -> points to multiple artifact.jar's
compositeContent.jar          -> points to multiple content.jar's
milestones.RC1/
               artifacts.jar
               content.jar
               features/...
               plugins/...
milestones.RC2/
               artifacts.jar
               content.jar
               features/...
               plugins/...
...
</pre></code>

== Moving the packages from build to download ==

The packages need to be copied from the build server to the download area, they must be renamed, MD5 and SHA1 checksums must be generated, etc. To make this step easier there is a little script that does all the necessary steps. The script is called <tt>releaseRename.sh</tt> and is available in the EPP CVS: [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epp/releng/org.eclipse.epp.config/tools/releaseRename.sh?root=Technology_Project&content-type=text%2Fplain&view=co releaseRename.sh]

The script is usually checked out on build.eclipse.org in <tt>EPP_BuildDirectory/epp_build/35/org.eclipse.epp/releng/org.eclipse.epp.config/tools/releaseRename.sh</tt> and takes two parameters: The BuildID and the kind of the release, e.g. M6, RC1, R, SR1, etc.

<pre>
sh releaseRename.sh 20090605-1619 RC3
</pre>

Note that there are some preset values in the script which need to be modified from time to time, or to be more precise from release train to release train.

<pre>
# the target directory
RELEASEDIRECTORY=/home/data/httpd/download.eclipse.org/technology/epp/downloads/release
# the directory where the packages are being build and available in a subdirectory for every build id, e.g. 20090605-1619/
TESTDIRECTORY=/shared/technology/epp/epp_build/35/download
# name of the release train
RELEASETRAIN=galileo
...
</pre>

The script creates the necessary directories, copies the logfiles, the XML configuration files, copies and renames the package files, and calculates the checksum files for each package.

== After the release ==

* update <tt>EPP_DownloadDir/downloads/release/staging.xml</tt> and send a mail to Nathan.
* copy <tt>EPP_DownloadDir/downloads/release/staging.xml</tt> to <tt>EPP_DownloadDir/downloads/release/release.xml</tt> after contacting Nathan.

=== Format of release.xml, staging.xml ===

Both files control the Drupal CMS and point to past/present/future releases of the EPP packages, e.g. <tt>galileo/RC2</tt> is the relative path to the RC2 packages of the Galileo release.

<pre>
<packages>
  <past>ganymede/R</past>
  <past>ganymede/SR1</past>
  <present>ganymede/SR2</present>
  <future>galileo/RC1</future>
  <future>galileo/RC2</future>
</packages>
</pre>

=== Update of scripts, etc. for the next release ===

* <tt>startXY.sh</tt> script in [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epp/releng/org.eclipse.epp.config/?root=Technology_Project org.eclipse.epp/releng/org.eclipse.epp.config]
** Check the p2 repositories and their location
** Update <tt>RELEASE_NAME</tt> variable, e.g <tt>RELEASE_NAME="-galileo-RC3"</tt>
* ALL package definitions in [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epp/packages/?root=Technology_Project org.eclipse.epp/packages]
** in the feature projects, the <tt>eclipse_PACKAGENAME_galileo.xml</tt>
*** especially <rcp version="3.5RC4" /> and <product name="eclipse-java-galileo-RC4" ...
** the definition of the Eclipse SDK which is in another location ([http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epp/releng/org.eclipse.epp.config/eclipse_sdk_galileo.xml?root=Technology_Project&view=markup org.eclipse.epp/releng/org.eclipse.epp.config/eclipse_sdk_galileo.xml])
* (manually) Check-out all new versions of the files on the build server build.eclipse.org
* Update the Eclipse that is used to build the packages in EPP_BuildDirectory/epp_build/35 to the latest <tt>eclipse-SDK-3.5XXX-linux-gtk-ppc.tar.gz</tt>




[[Category:EPP]]