You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by de...@apache.org on 2013/08/08 23:53:49 UTC
svn commit: r1512061 - in /sis/site/trunk/content:
release-management-setup.mdtext release-management.mdtext
Author: desruisseaux
Date: Thu Aug 8 21:53:49 2013
New Revision: 1512061
URL: http://svn.apache.org/r1512061
Log:
Updated release management instructions according experience gained.
Modified:
sis/site/trunk/content/release-management-setup.mdtext
sis/site/trunk/content/release-management.mdtext
Modified: sis/site/trunk/content/release-management-setup.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management-setup.mdtext?rev=1512061&r1=1512060&r2=1512061&view=diff
==============================================================================
--- sis/site/trunk/content/release-management-setup.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management-setup.mdtext [UTF-8] Thu Aug 8 21:53:49 2013
@@ -37,13 +37,15 @@ However in the later case, all relative
├─ trunk
├─ branches
├─ tags
- └─ distribution
+ ├─ distribution
+ └─ site
Create the above directory structure as below:
:::bash
svn checkout https://svn.apache.org/repos/asf/sis/trunk
svn checkout https://dist.apache.org/repos/dist/dev/sis distribution
+ svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
mkdir branches
mkdir tags
Modified: sis/site/trunk/content/release-management.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management.mdtext?rev=1512061&r1=1512060&r2=1512061&view=diff
==============================================================================
--- sis/site/trunk/content/release-management.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management.mdtext [UTF-8] Thu Aug 8 21:53:49 2013
@@ -62,9 +62,12 @@ in this page shall be adjusted according
│ └─ $NEW_VERSION
│ └─ target
│ └─ bundles
- └─ distribution
- └─ $NEW_VERSION
- └─ RC$RELEASE_CANDIDATE
+ ├─ distribution
+ │ └─ $NEW_VERSION
+ │ └─ RC$RELEASE_CANDIDATE
+ └─ site
+ └─ content
+ └─ apidocs
@@ -267,10 +270,10 @@ Click on that file and verify that the c
In particular, all Java code snippets are missing if the `@preformat` taglet had not be properly registered,
so try to see at least one code snippet.
-Delete all `org/apache/sis/parent/$NEW_VERSION/sis-$NEW_VERSION-source-release.zip.*` files on the Nexus repository.
+Delete all `org/apache/sis/parent/$NEW_VERSION/parent-$NEW_VERSION-source-release.zip.*` files on the Nexus repository.
They should not be there - source release will be deployed on an other repository later.
-Delete all `org/apache/sis/**/$NEW_VERSION/site.xml.*` files.
+Delete all `org/apache/sis/*/$NEW_VERSION/*-$NEW_VERSION-site.xml.*` files.
There is no apparent reason for deploying Maven web site descriptors.
Close the Nexus staging repository: click the checkboxes for the open staging repositories
@@ -287,55 +290,83 @@ Announce on the `dev@` mailing list the
Stage the source, binary and javadoc artifacts {#stage}
==========================================================
-Create the directory for the new version and release candidate within the distribution directory.
-The `$RELEASE_CANDIDATE` number shall correspond to the current release attempt.
-
- :::bash
- mkdir ../../distribution/$NEW_VERSION
-
-Create and put the binary artifact in the distribution directory:
+Create the binary artifact (`pack.gz` file):
:::bash
mvn org.apache.sis.core:sis-build-helper:$NEW_VERSION:pack --non-recursive
- mv target/bundles ../../distribution/$NEW_VERSION/RC$RELEASE_CANDIDATE
-Create and put the javadoc in the distribution directory:
+Generate the Javadoc. While not mandatory, we suggest to use JDK 7 or above for getting the new look and feel,
+getting the Javadoc enhancements expected in future JDK releases (more dynamic pages),
+avoiding the security vulnerability discovered in the Javadoc tools of older JDK releases,
+and keeping the `diff` smaller on the SVN repository of SIS web site.
+If JDK7 is *not* used, then omit the `cp` command below.
:::bash
+ cp ../../JDK7/src/main/javadoc/stylesheet.css src/main/javadoc/
+ mvn site
+ svn revert src/main/javadoc/stylesheet.css
cd target/site
- zip -9 -r ../../../../distribution/$NEW_VERSION/RC$RELEASE_CANDIDATE/sis-$NEW_VERSION-apidocs.zip apidocs
+ zip -9 -r apache-sis-$NEW_VERSION-doc.zip apidocs
cd ../..
-Create and put the source code in the distribution directory:
+Create the directory for the new version and release candidate within the distribution directory.
+The `$RELEASE_CANDIDATE` number shall correspond to the current release attempt.
:::bash
- svn export . ../../distribution/$NEW_VERSION/RC$RELEASE_CANDIDATE/src --native-eol LF
- cd ../../distribution/$NEW_VERSION/RC$RELEASE_CANDIDATE
- zip -9 -r sis-$NEW_VERSION-src.zip src
- rm -r src
+ cd ../../distribution
+ mkdir -p $NEW_VERSION/RC$RELEASE_CANDIDATE
+ svn add $NEW_VERSION
+
+Copy the `HEADER.html` file from the previous release.
+Update the file content if necessary.
+
+ cd $NEW_VERSION/RC$RELEASE_CANDIDATE
+ svn copy https://dist.apache.org/repos/dist/release/sis/$OLD_VERSION/HEADER.html .
+
+Move the files generated by Maven to the distribution directory:
+
+ mv ../../../tags/$NEW_VERSION/target/sis-$NEW_VERSION-* .
+ mv ../../../tags/$NEW_VERSION/target/site/apache-sis-$NEW_VERSION-* .
+
+Rename the files to something more conform to the convention seen in other Apache projects:
+
+ mv sis-$NEW_VERSION-source-release.zip apache-sis-$NEW_VERSION-src.zip
+ mv sis-$NEW_VERSION-source-release.zip.asc apache-sis-$NEW_VERSION-src.zip.asc
Sign the source, javadoc and binary artifacts:
:::bash
- gpg --armor --detach-sign sis-$NEW_VERSION.src.zip
- gpg --print-md SHA512 sis-$NEW_VERSION.src.zip > sis-$NEW_VERSION.src.zip.sha
- gpg --print-md MD5 sis-$NEW_VERSION.src.zip > sis-$NEW_VERSION.src.zip.md5
- gpg --armor --detach-sign sis-$NEW_VERSION.apidocs.zip
- gpg --print-md SHA512 sis-$NEW_VERSION.apidocs.zip > sis-$NEW_VERSION.apidocs.zip.sha
- gpg --print-md MD5 sis-$NEW_VERSION.apidocs.zip > sis-$NEW_VERSION.apidocs.zip.md5
- gpg --armor --detach-sign sis-$NEW_VERSION.pack.gz
- gpg --print-md SHA512 sis-$NEW_VERSION.pack.gz > sis-$NEW_VERSION.pack.gz.sha
- gpg --print-md MD5 sis-$NEW_VERSION.pack.gz > sis-$NEW_VERSION.pack.gz.md5
+ gpg --print-md SHA512 apache-sis-$NEW_VERSION-src.zip > apache-sis-$NEW_VERSION-src.zip.sha
+ gpg --print-md MD5 apache-sis-$NEW_VERSION-src.zip > apache-sis-$NEW_VERSION-src.zip.md5
+ gpg --armor --detach-sign apache-sis-$NEW_VERSION-doc.zip
+ gpg --print-md SHA512 apache-sis-$NEW_VERSION-doc.zip > apache-sis-$NEW_VERSION-doc.zip.sha
+ gpg --print-md MD5 apache-sis-$NEW_VERSION-doc.zip > apache-sis-$NEW_VERSION-doc.zip.md5
+ gpg --armor --detach-sign apache-sis-$NEW_VERSION.pack.gz
+ gpg --print-md SHA512 apache-sis-$NEW_VERSION.pack.gz > apache-sis-$NEW_VERSION.pack.gz.sha
+ gpg --print-md MD5 apache-sis-$NEW_VERSION.pack.gz > apache-sis-$NEW_VERSION.pack.gz.md5
Commit:
:::bash
cd ../..
- svn add $NEW_VERSION
svn commit --message "SIS release candidate $RELEASE_CANDIDATE"
Verify that the files are downloadable from the
-[http://dist.apache.org/repos/dist/dev/sis/][http://dist.apache.org/repos/dist/dev/sis/] sub-directory.
+[https://dist.apache.org/repos/dist/dev/sis/][https://dist.apache.org/repos/dist/dev/sis/] sub-directory.
+
+Copy the Javadoc to the web site staging directory:
+
+ :::bash
+ cd ../site/content
+ rm -r apidocs
+ unzip ../../distribution/0.3/RC1/apache-sis-0.3-doc.zip
+
+Execute `svn add` for new files and `svn remove` for deleted files:
+
+ :::bash
+ cd apidocs
+ svn status | gawk '/^\?.*/ {print $2}' | xargs -r svn add
+ svn status | gawk '/^\!.*/ {print $2}' | xargs -r svn remove