Author: apadilla
Date: Mon Mar 7 08:56:49 2011
New Revision: 1078716
URL: http://svn.apache.org/viewvc?rev=1078716&view=rev
Log:
* updated release process documentation
* fixed parsing error in some apt files
Modified:
incubator/npanday/trunk/site/src/site/apt/developers/building-on-64bit.apt
incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
incubator/npanday/trunk/site/src/site/apt/guide/installation/index.apt.vm
Modified:
incubator/npanday/trunk/site/src/site/apt/developers/building-on-64bit.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/developers/building-on-64bit.apt?rev=1078716&r1=1078715&r2=1078716&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/developers/building-on-64bit.apt
(original)
+++ incubator/npanday/trunk/site/src/site/apt/developers/building-on-64bit.apt
Mon Mar 7 08:56:49 2011
@@ -27,4 +27,4 @@ Building NPanday on 64bit-Windows
all frameworks in <<<.m2\npanday-settings.xml>>>.
We expect to enable native support for building with 32-bit even on 64-bit
operating systems in the next version
- of NPanday, though. For Details see
{{{https://issues.apache.org/jira/browse/NPANDAY-369}} NPANDAY-369}.
\ No newline at end of file
+ of NPanday, though. For Details see
{{{https://issues.apache.org/jira/browse/NPANDAY-369} NPANDAY-369}}.
\ No newline at end of file
Modified: incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt?rev=1078716&r1=1078715&r2=1078716&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
(original)
+++ incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt Mon Mar
7 08:56:49 2011
@@ -22,7 +22,11 @@ Pre-release checklist
* Check the build is successful for both NPanday and NPanday-ITs
- * Ensure all issues in the tracker for that version have been resolved, or
are moved to a later version
+ * Ensure all issues in the jira for that version have been resolved, or are
moved to a later version
+
+ * NPanday staging repo
{{http://vmbuild.apache.org/archiva/repository/staged-npanday/}} should be
re-created before the release to ensure that the repo only contains the
+ artifacts for the said release version.
+
* Make sure that the copyright and licenses are on all source code
@@ -71,9 +75,9 @@ mvn release:prepare
[[3]] Fill in the following values:
- * the release version should be <<<1.2.1-RC1>>> or similar (use the release
version)
+ * the release version should be <<<1.3.1-incubating>>> or similar (use the
release version)
- * the SCM tag should be <<<npanday-1.2.1-RC1>>> or similar (use the release
version)
+ * the SCM tag should be <<<npanday-1.3.1-incubating>>> or similar (use the
release version)
* check the values for the <Release version> and <Next development version>
are correct
@@ -97,9 +101,9 @@ mvn release:prepare
[[3]] Fill in the following values:
- * the release version should ve <<<1.2.1-RC1>>> or similar (use the release
version)
-
- * the SCM tag should be <<<npanday-its-1.2.1-RC1>>> or similar (use the
release version)
+ * the release version should ve <<<1.3.1-incubating>>> or similar (use the
release version)
+
+ * the SCM tag should be <<<npanday-its-1.3.1-incubating>>> or similar (use
the release version)
* check the values for the <Release version> and <Next development version>
are correct
@@ -111,12 +115,12 @@ mvn release:prepare
mvn release:perform -Pnpanday-release -Dtag=url_tag
----
- To verify if the release was successful, check that the artifacts has been
populated in {{http://repo.npanday.org/archiva/repository/npanday-releases/}}
+ To verify if the release was successful, check that the artifacts has been
populated in {{http://vmbuild.apache.org/archiva/repository/staged-npanday/}}
Testing the Release Candidate
- Announce the RC and the community will be given a 48hr window to test. If
the RC passes, same process would be done
- for the final version. eg. <<<1.2.1>>>.
+ Announce the RC and the community will be given a 72hr window to test. If
the RC passes, same process would be done
+ for the final version. eg. <<<1.3.1-incubating>>>.
Voting on the Release
@@ -128,11 +132,23 @@ Finalising the Release
* {{{./publishing-docs.html} Publish the site}} for the released version
- * Update Download Page to upload the repository builder from the latest
release and mark the version as released
+ * Binaries and sources should be copied to
<<<//www/www.apache.org/dist/incubator/npanday/>>>.
+
+ * Artifacts should be merged and synched to ibiblio by executing the ff
command:
+
+----
+mvn stage:copy
-Dsource="http://vmbuild.apache.org/archiva/repository/staged-npanday/";
-Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
+-Dversion=1.3.1-incubating -DrepositoryId=apache.releases
+----
+
+ * Send out an announcement of the release to:
+
+ ** [email protected]
+
+ ** [email protected]
- * Make the announcement on the forum
[]
<<Note:>> If a serious flaw is found in the release, the release version
will not be removed in the distribution list
- but instead a new release (1.2.2) should be provided.
+ but instead a new release (1.3.2-incubating) should be provided.
Modified:
incubator/npanday/trunk/site/src/site/apt/guide/installation/index.apt.vm
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/guide/installation/index.apt.vm?rev=1078716&r1=1078715&r2=1078716&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/guide/installation/index.apt.vm
(original)
+++ incubator/npanday/trunk/site/src/site/apt/guide/installation/index.apt.vm
Mon Mar 7 08:56:49 2011
@@ -33,7 +33,7 @@ Pre-requisites
* Visual Studio 2005 (SP1) or the .NET 2.0 SDK for developing .NET 2.0
applications and libraries
- * Visual Studio 2008 (SP1) or the
{{{http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en}}
Windows 7 SDK for .NET 3.5 SP1 } for developing .NET 3.5 (and earlier)
applications and
+ * Visual Studio 2008 (SP1) or the
{{{http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en}
Windows 7 SDK for .NET 3.5 SP1 }} for developing .NET 3.5 (and earlier)
applications and
libraries
If you later have problems relating to being unable to find the SDK, refer
to the
