Build distribution Code Block |
---|
cd tags/$RELEASE-$RC/distribution/all
mvn -Psource
mvn
|
Copy the distribution to somewhere and try it Code Block |
---|
cd tags/$RELEASE-$RC/distribution/all/target
cp apache-tuscany-sca-all-$RELEASE.zip <someplace>
cp apache-tuscany-sca-all-$RELEASE-src.zip <someotherplace>
|
Try all the samples/demos The war samples are currently to be tested with - Tomcat 5.5.20 and Tomcat 6.0.14
- Jetty 6.1.3
- Geronimo 2.0.2 Tomcat6 jee5
- WebSphere 6.1 fix pack 9+
Clean you local repo of SCA modules and compile the source distro and run some samples. As you will have deleted the maven-tuscany-plugin artifact, you'll need to do a 3 part manual maven build, building in the modules directory, then the maven directory, and finally the samples directory. Check for copyrights in the code to ensure that are what you are expecting Code Block |
---|
grep \-iR \--exclude=LICENSE \--exclude=NOTICE Copyright * \| awk '{if (\!match($0, ".+ASF.+")) {print $0}}'
|
check all the NOTICE files Code Block |
---|
for i in `find . \-name NOTICE`; do echo XXXXXXXXXXXXXXXXXXXXXXXXXXXX; echo $i; cat $i; done > ../tmp
|
Check for any SNAPSHOTS left in by mistake Code Block |
---|
grep \-r \--include=*.xml SNAPSHOT *
|
Check the LICENSE file against what is provided in the distributions. There is no automation for this bit. Check that all jars in the distribution\lib is mentioned on the binary LICENSE Code Block |
---|
for fn in `find . -name "*.jar" \-printf "%f\n"`; do if grep \-q $fn ../LICENSE; then "-"; else "$fn NOT present"; fi; done;
|
And check that all jars that are mentioned are present Code Block |
---|
for fn in `awk '/.jar/ {if (match($0,"[a-zA-Z0-9._\-|a-zA-Z0-9._-]+[.]jar")) {print substr($0, RSTART,RLENGTH) } }' ../LICENSE`; do if ls * \| grep -q $fn; then echo "-";else echo ">>> $fn NOT present"; fi; done
|
Check for junk included by accident Code Block |
---|
find . \-name log \-print
find . \-name work \-print
find . \-name lck \-print
find . \-name activemq-data \-print
find . \-name temp \-print
find . \-name tmp \-print
|
Generate the RAT reportsUnpack a binary and source distribution archive and create rat reports for each. Code Block |
---|
java \-jar $RATJAR srcExtractionDir > rat-$RELEASE-$RC-src.txt
java \-jar $RATJAR binExtractionDir > rat-$RELEASE-$RC-bin.txt
|
Copy the reports up onto the staging repo. You should of course check the report at this stage. Code Block |
---|
$SCPCOMMAND rat-$RELEASE-$RC.txt $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
|
Note |
---|
| If you need to regenerate the RAT report after you have started on the steps that follow run "mvn clean" first to avoid complains about the files under target folders |
Once you are happy with the release artifacts you can sign them and make them available from review. Sign the artifactsLinux Code Block |
---|
cd tags/$RELEASE-$RC/distribution/target
for i in *.zip *.gz; do gpg --output $i.asc --detach-sig --armor $i; done
for i in *.zip *.gz; do openssl md5 -hex $i \| sed 's/MD5((**[\^)|]*))= ([0-9a-f|0-9a-f]\*)/\2 \*\1/' > $i.md5; done
|
Windows: Code Block |
---|
for %A in (*.zip) do gpg \--output %A.asc \--detach-sig \--armor %A
for %A in (*.gz) do gpg \--output %A.asc \--detach-sig \--armor %A
for %A in (*.zip) do gpg \--print-md md5 %A > %A.md5
for %A in (*.gz) do gpg \--print-md md5 %A > %A.md5
|
The commands above should produce artifacts of an appropriate format, as follows. md5 should look like Code Block |
---|
8fb7cb398063ed0dffa414168468fffc \*apache-tuscany-sca-1.1-incubating.zip
|
asc should look like Code Block |
---|
\---\--BEGIN PGP SIGNATURE-\---\-
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQBHnLGGE8fTrnkHPxIRAqPmAJ4tOR6W663FKCXHPi1GlLBWDyZwJgCeMqbb
68DOq0YsU/O7kJsBHuZXhJw=
=elh0
\---\--END PGP SIGNATURE-\---\-
|
Put the artifacts up in your home directory on people.apache.org Code Block |
---|
cd tags/$RELEASE-$RC/distribution/target
$SCPCOMMAND *.asc $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
$SCPCOMMAND *.md5 $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
$SCPCOMMAND *.zip $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
$SCPCOMMAND *.gz $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
|
Code Block |
---|
cd tags/$RELEASE-$RC/distribution/src/main/release
pscp RELEASE_NOTES $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
pscp CHANGES $PAOUSER@people.apache.org:public_html/sca-java/$RELEASE/$RC/
|
Check permissions on the files Code Block |
---|
chmod 644 \*.zip
chmod 644 \*.gz
chmod 644 \*.txt
|
Deploy the maven artifacts locallyAs a potentially simpler alternative to deploying directly to p.a.o you can do the following (I have to use this approach as I can't get mvn to authenticate with p.a.o properly during deployment) Build the maven release artifact to a local directory (in this case target/deploy at the top level): Code Block |
---|
cd tags/$RELEASE-$RC
mvn -Prelease -DaltDeploymentRepository=id::default::file:target/deploy
|
Copy the artifacts up to p.a.o: Code Block |
---|
cd cd tags/$RELEASE-$RC/target/deploy
scp -r org slaws@people.apache.org:./public_html/tuscany/2.0-beta1-RC2/maven
|
Deploy the maven artifacts directly to p.a.oNote below that the reference to "me.people" in the "id" part of the -DaltDeploymentRepository argument to the maven deploy plugin is simply an identifier relating to a stanza in your local maven repo's settings.xml file. Note that also if you use ssh authentication by referencing a file containing your private key from the settings.xml file, then be sure to use a file in open ssh format. People who have followed the apache instructions for creating ssh keys on Windows with putty will probably not have created open ssh format files. You can however convert your .ppk file to the open ssh format by loading it into puttygen and using the conversion menu. Create a maven directory in your target directory on people.apache.org Code Block |
---|
cd tags/$RELEASE-$RC
mvn -N -DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/$PAOUSER/public_html/sca-java/$RELEASE/$RC/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=$PASSPHRASE
cd modules
mvn clean
mvn \-DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/$PAOUSER/public_html/sca-java/$RELEASE/$RC/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=$PASSPHRASE
cd shades (note, I thought it was only shades/base that needed doing, but the maven plugin failed on shades artifacts, so I deployed from shades)
mvn clean
mvn \-DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/$PAOUSER/public_html/sca-java/$RELEASE/$RC/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=$PASSPHRASE
cd maven/maven-tuscany-plugin
mvn clean
mvn \-DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/$PAOUSER/public_html/sca-java/$RELEASE/$RC/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=$PASSPHRASE
cd features
mvn clean
mvn \-DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/$PAOUSER/sca-java/$RELEASE/$RC/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=$PASSPHRASE
|
Deploy source jars Code Block |
---|
cd modules
mvn -Psource -DaltDeploymentRepository=me.people::default::scp://people.apache.org/home/kelvingoodson/public_html/sca-java/2.0-M5/RC3/maven -Dgpg.passphrase=$PASSPHRASE deploy
|
Check permissions of maven artifactsIf you've copied the maven artifacts up to p.a.o manually you may need to fix the permissions of the directories Code Block |
---|
find . -type d -exec chmod 755 {} \;
|
and files Code Block |
---|
find . -type f -exec chmod 644 {} \;
|
Check that the Maven artifacts workPoint you maven build at your p.a.o dir as a temporary mirror, for example, add mirror element to the settings.xml file (usually found at .m2/settings) Code Block |
---|
<mirrors>
<mirror>
<id>ant.staging</id>
<url>http://people.apache.org/~<PAOUSER>/sca-java/<release>/<RC>/maven</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
|
Clean you local SCA artifacts and use maven to compile samples and see if they run. Check in the tag Code Block |
---|
cd tags
svn copy $RELEASE-$RC https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/tags/$RELEASE-$RC -m "Tag for $RELEASE $RC"
|
Start votingThe PPMC will vote first. This may give rise to a new release candidate being required. If so you need to go back and start at the "Create Tag" step but using the next RC number. Once the PPMC vote is complete the vote is moved across to the IPMC. Once all the votes are complete the artifacts that have been voted on can be release. Once all the voting is completeCopy the artifacts from you directory on people.apache.org to; Code Block |
---|
/www/www.apache.org/dist/tuscany/java/sca/$RELEASE
|
Also check that the KEYS file is up to date. Code Block |
---|
/www/www.apache.org/dist/tuscany
|
Copy the staging repo to the live repoOption 1 (untested for 2.0-M5) Code Block |
---|
mvn stage:copy -Dsource="http://people.apache.org/~slaws/tuscany/1.1-RC3a/maven" -Dtarget="scp://<userid@>people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" -Dversion=1.1
|
You'll need the maven stage plugin to do this. Since maven-stage-plugin is not published, the release manager should checkout the source for the plugin and build it. Code Block |
---|
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-stage-plugin/
|
Or option 2 (used for 2.0-M5), instead of using the Maven stage plugin just manually copy the artifacts there: Code Block |
---|
cd public_html/sca-java/$RELEASE/$RC/org/apache/tuscany/
cp -p -v -R sca/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/sca
cp -p -v -R maven/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/maven
|
Check the permissions in the repoThere is a script in the SNAPSHOT report that sets the permissions correctly; take a look at the contents of the script and adjust for your purposes Code Block |
---|
more /www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
|
For example: Code Block |
---|
cd /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/
find . ! -perm 775 -type d -user ${USER} -exec chmod 775 {} \; -print
find . ! -perm 664 -iname maven-metadata.xml* -user ${USER} -exec chmod 664 {} \; -print
find . -group slaws -exec chgrp committers {} \; -print
|
Copy the release candidate tag to the final tag name. Code Block |
---|
svn copy https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/tags/$RELEASE-$RC/ https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/tags/$RELEASE -m "Copy $RC tag as final release tag"
|
|