svn commit: r1646894 - in /maven/site/trunk: ./ content/apt/developers/release/ content/markdown/developers/ content/markdown/developers/release/ content/markdown/docs/3.2.5/

[jv...@apache.org]

Author: jvanzyl
Date: Fri Dec 19 22:23:55 2014
New Revision: 1646894

URL: http://svn.apache.org/r1646894
Log:
Update for Maven 3.2.5
Convert core release documentation to Markdown

Added:
    maven/site/trunk/content/markdown/developers/
    maven/site/trunk/content/markdown/developers/release/
    maven/site/trunk/content/markdown/developers/release/maven-core-release.md
    maven/site/trunk/content/markdown/docs/3.2.5/
    maven/site/trunk/content/markdown/docs/3.2.5/release-notes.md
Removed:
    maven/site/trunk/content/apt/developers/release/maven-core-release.apt
Modified:
    maven/site/trunk/pom.xml

Added: maven/site/trunk/content/markdown/developers/release/maven-core-release.md
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/developers/release/maven-core-release.md?rev=1646894&view=auto
==============================================================================
--- maven/site/trunk/content/markdown/developers/release/maven-core-release.md (added)
+++ maven/site/trunk/content/markdown/developers/release/maven-core-release.md Fri Dec 19 22:23:55 2014
@@ -0,0 +1,116 @@
+## Releasing Maven
+
+Maven differs slightly in its release process due to several extra steps.
+
+The goal is to commit candidate release to svn tree <https://dist.apache.org/repos/dist/dev/maven/maven-3>/`$VERSION`. Then once the vote passed, svn move to <https://dist.apache.org/repos/dist/release/maven/maven-3>/`$VERSION`.
+
+The tree directory is:
+
+- https://dist.apache.org/repos/dist/release/maven/maven-3/`$VERSION`/binaries
+- https://dist.apache.org/repos/dist/release/maven/maven-3/`$VERSION`/source
+
+Note that the policy for failed releases is to move forward with a new
+version. The tag that produced the failed released is left in place for
+posterity. So if the release of, say, 3.2.4 fails then we move forward
+with 3.2.5.
+
+### Produce Release Candidates
+
+For non-alpha/beta releases, release candidates are produced before the actual release.
+
+Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create the necessary directory tree.
+
+Copy the binaries and src-tar.gz with their md5/asc to the created directories.
+
+To produce a release candidate, follow the first seven steps only from the following procedure:
+
+-   [Maven Project Common Release Procedure](./maven-project-release-procedure.html)
+
+The version used should be the eventual version with -RC1, -RC2, etc. appended.
+
+After producing the RC, request that the developers test the release on the list. If a regression is found, a new release candidate is rolled.
+
+After a reasonable time without regressions found, a wider audience may be polled if the release manager desires (for example, users@).
+
+Once happy with a release candidate, the full release is performed, with the final version in place.
+
+### Produce the Release
+
+To produce a final release, the same process as for standard projects is followed:
+
+-   [Maven Project Common Release Procedure](./maven-project-release-procedure.html)
+
+Below describes the additional steps that need to be taken at the points where the website are updated in those instructions.
+
+#### Update the DOAP Information
+
+Edit <https://github.com/apache/maven/blob/master/doap_Maven.rdf> to list the new release.
+
+#### Update the Release Notes and Web Site
+
+Checkout <https://svn.apache.org/repos/asf/maven/site/trunk>.
+
+Note that release notes can be created and checked in, but other changes should not be checked in as it can be deployed 'live' at any time.
+
+- For 3.x: update the `versions3x`, `currentStableVersion` and `currentStableReleaseDate` properties in `pom.xml`
+
+Next, create the release notes:
+
+- create `docs/$version`
+- populate `docs/$version/release-notes.txt` from JIRA
+- create `docs/$version/release-notes.apt.vm` (see other versions for an example)
+
+Next, update release history `docs/history.apt`.
+
+Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to [/ref/](/ref).
+
+#### Stage the Latest Documentation
+
+Once the release is prepared, but before the release vote, the site needs to be staged.
+
+From the release checkout, stage the site:
+
+```
+mvn -Preporting site site:stage
+mvn scm-publish:publish-scm
+```
+
+This will publish the site in [/ref/3-LATEST](/ref/3-LATEST).
+
+#### Add New Version to ASF Distribution Directory
+
+In addition to promoting the repository, the release archives should be
+moved to the release svnpubsub tree:
+
+```
+svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION https://dist.apache.org/repos/dist/release/maven/maven-3
+```
+
+#### Deploy the Current Reference
+
+The source code references and API docs need to be deployed before deploying the web site with the new version.
+
+This consists in copying in website svn tree the /ref/3-LATEST directory to /ref/`$VERSION`.
+
+```
+svn cp https://svn.apache.org/repos/infra/websites/production/maven/content/ref/3-LATEST https://svn.apache.org/repos/infra/websites/production/maven/content/ref/$VERSION
+```
+
+### Information on `/ref/current` mechanism
+
+The redirection from `/ref/current` to actual Maven version reference is done through `.htaccess` published in site.
+
+#### Deploying the Release Website
+
+Once both of the above have synced to the main site and a suitable number of mirrors, proceed to update the web site and produce the announcement.
+
+Commit your changes and then [deploy the main Maven site](../website/deploy-maven-website.html).
+
+#### Remove Old Versions from ASF Distribution Directory
+
+Next, any superceded releases should be removed from the above locations (after confirming that they exist in /www/archive.apache.org/dist/maven).
+
+#### Proceed with Announcement
+
+You can now proceed with the steps outlined after deploying the website on [Maven Project Common Release Procedure](./maven-project-release-procedure.html)
+

Added: maven/site/trunk/content/markdown/docs/3.2.5/release-notes.md
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/docs/3.2.5/release-notes.md?rev=1646894&view=auto
==============================================================================
--- maven/site/trunk/content/markdown/docs/3.2.5/release-notes.md (added)
+++ maven/site/trunk/content/markdown/docs/3.2.5/release-notes.md Fri Dec 19 22:23:55 2014
@@ -0,0 +1,55 @@
+# Release Notes &#x2013; Maven 3.2.5
+
+<!-- 
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
+-->
+
+## Maven 3.2.5
+
+The Apache Maven team would like to announce the release of Maven 3.2.5.
+
+Maven 3.2.5 is [available for download][0].
+
+Maven is a software project management and comprehension tool. Based on the concept of a project object model
+(POM), Maven can manage a project's build, reporting and documentation from a central place.
+
+Maven 3 aims to ensure backward compatibility with Maven 2, improve usability, increase performance, allow safe embedding, and pave the way to implement many highly demanded features.
+
+The core release is independent of the plugins available. Further releases of plugins will be made separately.
+See the [PluginList][1] for more information.
+
+We hope you enjoy using Maven! If you have any questions, please consult:
+
+- the web site: [http://maven.apache.org/](http://maven.apache.org/)
+- the maven-user mailing list: [http://maven.apache.org/mail-lists.html](http://maven.apache.org/mail-lists.html)
+- the reference documentation: [http://maven.apache.org/ref/3.2.5/](http://maven.apache.org/ref/3.2.5/)
+
+The full list of changes can be found in our [issue management system][4].
+
+## Complete Release Notes
+
+See [complete release notes for all versions][5]
+
+[0]: ../../download.html
+[1]: ../../plugins/index.html
+[2]: http://maven.apache.org/
+[4]: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&amp;version=20819
+[5]: ../../release-notes-all.html

Modified: maven/site/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?rev=1646894&r1=1646893&r2=1646894&view=diff
==============================================================================
--- maven/site/trunk/pom.xml (original)
+++ maven/site/trunk/pom.xml Fri Dec 19 22:23:55 2014
@@ -50,15 +50,15 @@
   </issueManagement>
 
   <properties>
-    <currentStableVersion>3.2.3</currentStableVersion>
-    <currentStableReleaseDate>2014-08-18</currentStableReleaseDate>
-    <current32xVersion>3.2.3</current32xVersion>
+    <currentStableVersion>3.2.5</currentStableVersion>
+    <currentStableReleaseDate>2014-12-20</currentStableReleaseDate>
+    <current32xVersion>3.2.5</current32xVersion>
     <current31xVersion>3.1.1</current31xVersion>
     <current30xVersion>3.0.5</current30xVersion>
     <currentAntTasksVersion>2.1.3</currentAntTasksVersion>
     <currentAntTasksReleaseDate>2011-04-17</currentAntTasksReleaseDate>
     <versions2x>2.2.1,2.2.0,2.1.0,2.0.11,2.0.10,2.0.9,2.0.8,2.0.7,2.0.6,2.0.5,2.0.4,2.0.3,2.0.2,2.0.1,2.0</versions2x>
-    <versions3x>3.2.3,3.2.2,3.2.1,3.1.1,3.1.0,3.1.0-alpha-1,3.0.5,3.0.4,3.0.3,3.0.2,3.0.1,3.0,3.0-beta-3,3.0-beta-2,3.0-beta-1,3.0-alpha-7,3.0-alpha-6,3.0-alpha-5,3.0-alpha-4,3.0-alpha-3</versions3x>
+    <versions3x>3.2.5,3.2.3,3.2.2,3.2.1,3.1.1,3.1.0,3.1.0-alpha-1,3.0.5,3.0.4,3.0.3,3.0.2,3.0.1,3.0,3.0-beta-3,3.0-beta-2,3.0-beta-1,3.0-alpha-7,3.0-alpha-6,3.0-alpha-5,3.0-alpha-4,3.0-alpha-3</versions3x>
     <site.output>${project.build.directory}/site</site.output>
   </properties>