Author: ilgrosso
Date: Sat Sep 3 17:29:54 2016
New Revision: 1759115
URL: http://svn.apache.org/viewvc?rev=1759115&view=rev
Log:
[OPENJPA-2628] Update how to publish to the /dist area (including cleaning up
older releases)
Modified:
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Modified:
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.mdtext?rev=1759115&r1=1759114&r2=1759115&view=diff
==============================================================================
---
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
(original)
+++
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Sat Sep 3 17:29:54 2016
@@ -6,7 +6,7 @@ Title: Apache Nexus Release Process 1.2.
We're starting to move our builds over to using the Apache Nexus repository
(repository.apache.org) for releasing SNAPSHOT and release artifacts.
More details on releasing artifacts and using Nexus can be found on the Maven
website at - <http://maven.apache.org/developers/release/apache-release.html>
-
+https://svn.apache.org/repos/infra/websites/production/openjpa/content/builds
1. Environment setup for releasing artifacts (same for SNAPSHOTs and
releases)
1. Increase the default Java heap available to Maven (required for Java SE
6)
@@ -282,13 +282,18 @@ Different arguments and steps are requir
3. Copy the distribution artifacts over to the distribution area. This
step is what will eventually populate the download mirrors.
- 1. ssh to people.apache.org and create the distribution folder
+ 1. checkout the distribution directory
+
+ $ svn co https://dist.apache.org/repos/dist/release/openjpa/
openjpa-dist
+ $ cd openjpa-dist
+
+ 2. create the release folder
- $ mkdir /www/www.apache.org/dist/openjpa/${RELEASE}
+ $ mkdir ${RELEASE}
+ $ cd ${RELEASE}
- 2. Update the assemblies in the distribution directory. For this,
we'll just wget copies of the released assemblies with their signatures and
hashes from the Apache repo:
+ 3. update the assemblies in the distribution directory. For this,
we'll just wget copies of the released assemblies with their signatures and
hashes from the Apache repo:
- $ cd /www/www.apache.org/dist/openjpa/${RELEASE}
$ wget --no-check-certificate
https://repository.apache.org/content/repositories/releases/\
org/apache/openjpa/apache-openjpa/${RELEASE}/apache-openjpa-${RELEASE}-source.zip
$ wget --no-check-certificate
https://repository.apache.org/content/repositories/releases/\
@@ -296,15 +301,16 @@ Different arguments and steps are requir
Along with the corresponding .asc, .md5, and .sha1 files for both
ZIP files above.
- 3. Update openjpa group access
-
- $ chgrp -R openjpa /www/www.apache.org/dist/openjpa/${RELEASE}
- $ chmod -R g+w /www/www.apache.org/dist/openjpa/${RELEASE}
+ 4. commit
+
+ $ cd ..
+ $ svn add ${RELEASE}
+ $ svn commit -m "Copying ${RELEASE} artifacts to the
distribution directory"
- 4. Remove the previous maintenance version from /dist directory, if
exists. Ie if you're publishing 2.0.1 you would remove 2.0.0. Verify that the
release being removed is in the distribution archives before removing.
+ 4. remove any previous maintenance versions, i.e. if you're publishing
2.0.1 you would remove 2.0.0. Verify that the release being removed is in the
distribution archives before removing.
- $ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
- $ rm -rf /www/www.apache.org/dist/openjpa/2.0.0
+ $ svn rm <any older release artifact (if present)>
+ $ svn commit -m "Cleaning up older releases"
4. Update the [JIRA
Releases](https://issues.apache.org/jira/plugins/servlet/project-config/OPENJPA/versions)
page to mark the version as "released", and set the date to the date that the
release was approved.
(You may need to make a new release entry for the next release.)
