EPP/Obsolete/Galileo Packages/Release Actions

Directories used in the description

• EPP_BuildDirectory = server build.eclipse.org, directory /shared/technology/epp
• EPP_DownloadDirectory = /home/data/httpd/download.eclipse.org/technology/epp

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 build.eclipse.org in EPP_BuildDirectory/epp_repo/galileo/epp.build/buildresult/org.eclipse.epp.allpackages.feature_1.2.0-eclipse.feature/site.p2/ and needs to be copied to a milestone subdirectory below EPP_DownloadDirectory/packages/galileo/
• Update compositeArtifacts.jar and compositeContent.jar

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

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/...
...

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 releaseRename.sh and is available in the EPP CVS: [asd]