You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tuscany.apache.org by co...@apache.org on 2008/02/09 15:47:00 UTC
[CONF] Apache Tuscany: Making releases (page edited)
Making releases (TUSCANY) edited by Simon Laws
Page: http://cwiki.apache.org/confluence/display/TUSCANY/Making+releases
Changes: http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=60576&originalVersion=9&revisedVersion=10
Content:
---------------------------------------------------------------------
{section:border=false}
{column:width=15%}
{include: Menus}
{column}
{column:width=85%}
h3. Getting Ready
[Setting up ssh]
[Create signing key]
[Get hold of RAT]
h3. Useful Resources
[Incubator release best practice | http://incubator.apache.org/guides/releasemanagement.html#best-practice]
[Incubator Policy | http://incubator.apache.org/incubation/Incubation_Policy.html]
[ASF Developer Guide | http://www.apache.org/dev/]
[ASF Release FAQ | http://www.apache.org/dev/release.html]
[ASF Release Licensing FAQ | http://www.apache.org/dev/release.html#license]
[ASF Release Signing | http://www.apache.org/dev/release-signing.html]
[ASF Comitters Guide | http://www.apache.org/dev/new-committers-guide.html#pgp]
[Henk's ASF Key Guide | http://people.apache.org/~henkp/]
[Surfnet Key Server | http://pgp.surfnet.nl/]
[MIT Key Server | http://pgp.mit.edu/]
[Raymond's release script| http://svn.apache.org/repos/asf/incubator/tuscany/java/etc/release-sca.sh]
h3. Release Process
The borrows many of the command from [Raymond's release script|http://svn.apache.org/repos/asf/incubator/tuscany/java/etc/release-sca.sh] but with a bit more explanation and a few more useful commands. The commands here we taken from when release 1.1 RC3a was under preparation. It's also fair to say that it's unlikely that you will want to run all of these commands in sequence as you generally end up repeating sections as release preparation progresses.
h4. Call for release
At some point someone in the community will call for a release based on the features and fixes that have been under development in the trunk. Typically the first stage in the release process is to decide on who is going to be the release manager, i.e. who is going to ensure that all the steps are taken to ensure a good release. This will typical involve someone volunteering and a vote on the dev list. The next thing is the create a branch where the code can be stabalized and testing can start on the release artifacts. It's useful to try and ensure that the code is complete as possible and that all the samples run before the branch is created. This removes the need for a lot of double fixing between the branch and the trunk.
h4. Create the branch
{code}
svn copy https://svn.apache.org/repos/asf/incubator/tuscany/java/sca https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-1.1 -m "Branch for 1.1"
{code}
Once the branch is created the version number in trunk can be updated.
h4. Fix up the branch work
First checkout the branch so that you can work on it. These commands assume that a local directory called "branches" is present.
{code}
cd branches
svn co https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-1.1/ 1.1-RC3a
{code}
Remove all the files that are not going to be part of the release, test all the samples and check all of the LICENSE and NOTICE files. Once the branch is at the stage where a release candidate can be created for testing prepare to make a tag.
h4. Create Tag 1.1-RC3a
These commands assume that a local directory called "tags" is present.
{code}
cd tags
svn co https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-1.1/ 1.1-RC3a
{code}
Notice that all we are doing here is just checking out the branch again. This allows any last minute fixes to be taken from the branch in subversion and allows the version numbers in the tag to be corrected without affecting the branch, assuming that more than one tag will be required to complete the release process.
h4. Change the version ID
The "-SNAPSHOT" is removed from the end of the version string. This ensures that the only thing building with the release version number on your PC is the tag being tested.
{code}
cd 1.1-RC3a
for i in `/usr/bin/find . -name "*.xml"`; do if grep 1.1-incubating-SNAPSHOT $i>/dev/null; then sed "s/1.1-incubating-SNAPSHOT/1.1-incubating/g" $i >/tmp/tmp.xml; cp /tmp/tmp.xml $i; fi; done
{code}
h4. Generate the RAT report
java -jar C:\simon\apps\rat-0.5.1\rat-0.5.1.jar 1.1-RC3a > rat-1.1-RC3a.txt
scp rat-1.1-RC3a.txt slaws@people.apache.org:public_html/tuscany/1.1-RC3a
* Build from top level
mvn -fae -o clean install
* Build the demos
mvn -fae -o clean install
* build distribution
mvn clean
cd distribution
Check that the "all" jar is in place
* Copy the distribution to somewhere and try it
Try the samples/demos
Compile the source distro
Compile samples from the maven artifacts
check for copyrights in the code to ensure that are what you are expecting
grep -iR Copyright *
check all the NOTICE files
for i in `find . -name NOTICE`; do echo XXXXXXXXXXXXXXXXXXXXXXXXXXXX; echo $i; cat $i; done > ../tmp
check for any SNAPSHOTS
grep -r --include=*.xml SNAPSHOT *
check the LICENSE file
Can't we do some automation?
check for junk
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
other useful commands
find . -name ipo.xsd | xargs cat
* sign artifacts
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]*\)/\2 *\1/' > $i.md5; done
* put up on p.a.o
scp *.asc slaws@people.apache.org:public_html/tuscany/1.1-RC3a
scp *.md5 slaws@people.apache.org:public_html/tuscany/1.1-RC3a
scp *.zip slaws@people.apache.org:public_html/tuscany/1.1-RC3a
scp *.gz slaws@people.apache.org:public_html/tuscany/1.1-RC3a
scp RELEASE_NOTES slaws@people.apache.org:public_html/tuscany/1.1-RC3a
scp CHANGES slaws@people.apache.org:public_html/tuscany/1.1-RC3a
check perms
chmod 644 *.zip
chmod 644 *.gz
chmod 644 *.txt
* Deploy mvn artifacts
cd 1.1-RC3a
mvn -N -DaltDeploymentRepository=apache.incubator::default::scp://people.apache.org/home/slaws/public_html/tuscany/1.1-RC3a/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=
cd tools
mvn clean
mvn -DaltDeploymentRepository=apache.incubator::default::scp://people.apache.org/home/slaws/public_html/tuscany/1.1-RC3a/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=
cd modules
mvn clean
mvn -DaltDeploymentRepository=apache.incubator::default::scp://people.apache.org/home/slaws/public_html/tuscany/1.1-RC3a/maven verify gpg:sign install:install deploy:deploy -Dgpg.passphrase=
* deploy all jar
cd bundle/target
mvn gpg:sign-and-deploy-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-sca-all -Dversion=1.1-incubating -Dpackaging=jar -Dfile=tuscany-bundle-1.1-incubating.jar -DrepositoryId=apache.incubator -Durl=scp://people.apache.org/home/slaws/public_html/tuscany/1.1-RC3a/maven -Dkeyname=slaws -Dpassphrase=
* check in the tag
svn copy 1.1-RC3a https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3a/ -m "Tag for 1.1-RC3a"
* send mail to start project vote
!!!!!!!!!!!!!!
* Once all the votes are complete
Copy the artifacts up to www.apache.org/dist/incubator/tuscany
scp KEYS slaws@people.apache.org:public_html/tuscany/1.1-RC3a
* copy the staging repo to the live incubating repo
mvn stage:copy -Dsource="http://people.apache.org/~slaws/tuscany/1.1-RC3a/maven" -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-incubating-repository" -Dversion=1.1
mvn stage:copy -Dsource="http://people.apache.org/~slaws/tuscany/1.1-RC3/maven" -Dtarget="scp://people.apache.org/home/slaws/tmp-repo" -Dversion=1.1
h4. How to run RAT?
1. Download the latest release from http://code.google.com/p/arat (It's moving back to Apache incubation now).
2. java -jar <rat-xxx.jar> <the root folder> > xxx.rat
{note:title="Tips}
Run "mvn clean" first to avoid complains about the files under target folders
{note}
h4. Signing artifacts:
Windows:
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
h4. Deploying to a staging area:
A single file:
mvn deploy:deploy-file \-DgroupId=org.apache.tuscany \-DartifactId=tuscany-sca-all \-Dversion=0.90-incubating \-Dpackaging=jar \-Dfile=tuscany-sca-all-0.90-incubating.jar \-DrepositoryId=me.people \-Durl=scp://people.apache.org/home/antelder/public_html/tuscany/0.90-rc2/maven
Maven modules:
C:\Tuscany\SVN\0.90-TAG\modules>mvn \-DaltDeploymentRepository=apache.incubator::default::scp://people.apache.org/home/antelder/public_html/t
uscany/0.90-rc2/maven deploy
h4. Typical Tuscany Java SCA Release Artifacts
Here are the artifacts that are typically released as part of a Java SCA Release. This is based on experiences with Releases 0.90 and 0.91.
\- After tagging the release download the tag and build it
\- Then build the distributions.
\- Move into the target folder of the 'distribution' and execute the commands under the section titled 'Signing Artifcats' on this wiki page (see above). This will create the required '.asc' and '.md5' for the distros.
\- Then using sftp client (psftp or FileZilla or ...), ftp the distros and the signature files to the maven staging area.
\- Next move over to the 'distribution\bundle\target' directory of the tag. In there copy the file 'tuscany-bundle-xxx-incubating.jar' to 'tuscany-sca-all-xxx-incubating.jar'. Then deploy the tuscany-sca-all-0.91-incubating.jar to the maven staging area using the single file command as mentioned above in section 'Deploying to staging area'. For example.
{noformat}
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-sca-all -Dversion=0.91-incubating -Dpackaging=jar
-Dfile=tuscany-sca-all-0.91-incubating.jar -DrepositoryId=me.people -Durl=scp://people.apache.org/home/svkrish/public_html/tuscany/0.91-rc3/maven
{noformat} - Finally move over to the head of the 'tag' and deploy the tuscany-sca pom file, again using the single file command. For example mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-sca -Dversion=0.91-incubating -Dpackaging=pom -Dfile=pom.xml -DrepositoryId=me.people -Durl=scp://people.apache.org/home/svkrish/public_html/tuscany/0.91-rc3/maven
{column}
{section}
---------------------------------------------------------------------
CONFLUENCE INFORMATION
This message is automatically generated by Confluence
Unsubscribe or edit your notifications preferences
http://cwiki.apache.org/confluence/users/viewnotifications.action
If you think it was sent incorrectly contact one of the administrators
http://cwiki.apache.org/confluence/administrators.action
If you want more information on Confluence, or have a bug to report see
http://www.atlassian.com/software/confluence
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-commits-help@ws.apache.org