db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tilma...@apache.org
Subject [db-jdo] branch master updated: Create HowToReleaseJDO.md
Date Mon, 17 Feb 2020 20:26:51 GMT
This is an automated email from the ASF dual-hosted git repository.

tilmannz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/db-jdo.git

The following commit(s) were added to refs/heads/master by this push:
     new 4b1535a  Create HowToReleaseJDO.md
4b1535a is described below

commit 4b1535a42a716897cb20a32428efa516034add4c
Author: Tilmann <tilmannz@apache.org>
AuthorDate: Mon Feb 17 20:26:46 2020 +0000

    Create HowToReleaseJDO.md
 HowToReleaseJDO.md | 254 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 254 insertions(+)

diff --git a/HowToReleaseJDO.md b/HowToReleaseJDO.md
new file mode 100644
index 0000000..77fbb54
--- /dev/null
+++ b/HowToReleaseJDO.md
@@ -0,0 +1,254 @@
+* link:#procoverview[Overview of the process]
+* link:#procdetail[Detailed process steps]
+* link:#site[Site updates]
+* link:#postrelease[Post release modifications and documentation]
+== How to Release an Apache JDO Distribution
+A distribution of JDO is built from a branch of svn. It is copied into a
+release directory, from which it is staged and tested prior to release.
+Once released, it is propagated to mirror servers around the world.
+The process is performed by a release manager with cooperation from
+testers in the community.
+=== Overview of the process
+The community first decides on the name of the release. The format of
+the name is _spec-number_._major_._minor_. A trailing _minor_ number
+with a zero value is right trimmed, so there might be a 2.0.1 but not a
+Interim releases prior to final release are identified by a suffix on
+the release number. Common suffixes include: -alpha, -beta, -beta2,
+-rc1, -rc2. Generally, the suffixes are part of the release plan, and
+the contents of each suffix release are agreed by the community. There
+might be significant changes in functionality between the suffix
+releases. Each suffix release goes through the process documented here.
+The release manager makes a branch from the trunk (for a major release)
+or from another branch (for a minor release) to create a branch with the
+source of the distribution.
+The release manager follows the Apache process detailed below to build
+and deploy a release.
+The release manager calls for the community to test the release.
+The community tests the release. If necessary, cycle until all issues
+are resolved.
+The release manager closes the staged repository
+The release manager calls for a vote to release by sending a message to
+the community and forwarding the message to the pmc.
+The community votes on the release. If necessary, cycle until issues are
+The release manager notifies the pmc of the successful vote outcome.
+Note that a successful vote includes three +1 votes from PMC members.
+The release manager notifies the worldwide community of the availability
+of the release.
+The release manager updates the JDO web sites
+(http://db.apache.org/jdo/index.html, http://java.sun.com/jdo/).
+If bugs are found or test challenges are sustained after the release is
+approved and distributed, the release manager creates a new branch to
+address the bugs found.
+=== Detailed process steps
+. You might want to run http://creadur.apache.org/rat[Apache Rat] to
+check the sources for any lisence issues.
+mvn apache-rat:check
+. Create a branch from the trunk and increment the spec or major number.
+For example, create a 3.1 branch from the trunk.
+cd jdo
+svn copy https://svn.apache.org/repos/asf/db/jdo/trunk \
+. In trunk, update version numbers in the following files in preparation
+for the next release:
+  File names and version references in the Overview section
+  Update version number and date
+Use the maven version plug-in to update version numbers in the pom.xml
+files at the root and subproject levels.
+. If needed, update the dependency to the RI, DataNucleus, in the tck
+. If needed, apply patches from the trunk or branches to the new branch.
+. Update version numbers where necessary in projects to be released, if
+these changes haven't been made previously. Check the following files:
+  File names and version references in the Overview section (for a major
+  release only.)
+  Update version number
+. Check the scm settings in the pom.xml files in the new branch and make
+sure they refer the new branch (instead of the trunk).
+. Follow the instructions at
+Maven Artifacts] to set up your development environment.
+. Copy the JNDI implementation jars (providerutil.jar and fscontext.jar)
+to the branch lib/ext directory. This is needed to test the tck before
+distributing it.* +
+Do not check these in to SVN*
+. Build the distribution with the following command:
+     mvn clean install -Papache-release
+This creates the .jar and .pom files in the target directory of each
+subproject. Be prepared to enter your key passcode when prompted. This
+happens multiple times.
+. Run http://creadur.apache.org/rat[Apache Rat] on the release.
+. Do a dry run prepare and deployment of a snapshot release. You might
+want to do this in a fresh workspace, since you cannot have local
+modifications when preparing a release. The files in lib/ext and
+lib/jdori count as local modifications. Be prepared to enter your key
+passcode when prompted. This happens multiple times.
+ mvn release:prepare -Papache-release -DautoVersionSubmodules=true -DdryRun=true -Dresume=false
+ mvn deploy -Papache-release 
+Check the artifacts at
+https://repository.apache.org/content/repositories/snapshots/[the Maven
+release repository]
+. Prepare and release the artifacts. There are interoperability issues
+with the maven release plugin and cygwin, so if on Windows, use a
+Windows command window for this step and the following one.
+mvn release:clean -Papache-release
+mvn release:prepare -Papache-release
+Note: If you're located in Europe then release:prepare may fail with
+'Unable to tag SCM' and ' svn: No such revision X '. Wait 10 seconds and
+run mvn release:prepare again.
+. Stage the release for a vote.
+mvn release:perform -Papache-release
+. Go to https://repository.apache.org/index.html[the Nexus repository],
+login with your apache account, click on Staging Repositories in the
+menu on the left and close the staged repository. Press the refresh
+button to see the new status 'closed'. See
+Closing an Open Repository] for details.
+. Send an announcement to test the release to the jdo-dev@db.apache.org
+alias. If problems are found, fix and repeat.
+. Send an announcement to vote on the release to the
+jdo-dev@db.apache.org alias. The message subject line contains [VOTE].
+Forward the [VOTE] message to private@db.apache.org. Iterate until you
+get a successful vote. Mail the results of the vote to
+jdo-dev@db.apache.org, cc: general@db.apache.org, and include [VOTE]
+[RESULTS] in the subject line.
+. After testing and voting is complete, follow the instructions at
+Releasing a Staging Repository] to release the artifacts.
+. Update the distribution repository at http://apache.org/dist/db/jdo/
+by adding the new release directory to the svnpubsub directory. Check
+out the repository at https://dist.apache.org/repos/dist/release/db/jdo
+and add the new release with all artifacts under the new directory. Make
+sure that the key used to sign the artifacts is included in the KEYS
+file. Committing the new directory will trigger an update to the
+. If the release is a bug fix release to a maintenance release, update
+README.txt in the parent branch, adding the following line: "This
+release has been deprecated. Please use version 2.x.y.", with a link to
+the svn web interface for that version.
+. After updating the site (below), announce the release to the Apache
+community via email to announce@apache.org This must be sent from an
+@apache.org email address. *** Be aware that by sending to this address
+you will be bombarded with piles of emails from people with "I'm out of
+the Office" as if you really cared ***
+=== Site updates
+. Update the Apache JDO web site to point the downloads page to the
+.. In site/src/site/xdoc/releases create release-_N.n_.xml. Edit the
+release numbers and the link to the release notes. You will need to
+change the '&'s in the URL to "&amp;"
+.. In site/src/site/resources/releases create release-_N.n_.cgi. The
+.cgi file contents are identical to the other .cgi files in the release
+directory; only the file name differs.
+.. Edit site/src/site/xdoc/downloads.xml to link to the new release page
+.cgi document.
+.. Build and test as described in the site/HOWTO document. Note that the
+cgi page will not be active until it is on the server, so can't really
+be tested.
+.. Add the new files to the subversion repository.
+svn add site/src/site/xdoc/releases/release-N.n.xml 
+svn add site/docs/releases/release-N.n.html 
+svn add site/src/site/resources/releases/release-N.n.cgi 
+svn add site/docs/releases/release-N.n.cgi 
+.. Set the svn properties svn:eol-style to native and svn:executable to
+true for the .cgi files.
+. Change the link to RunRules on the
+http://db.apache.org/jdo/tck.html[TCK] page to link to the RunRules.html
+file of the latest release.
+. Update the news list on the site home page to announce the new
+. Update the specification page to link to the new specification pdf
+document. If the release has been approved by the JCP, link to the
+documentation page of the JCP web site. If the release has not been
+approved by the JCP, link to the .pdf in the JDO source repository.
+. Add the javadoc for the release to the site.
+.. Make a new directory under site/docs for the release, e.g. api2.1.
+We'll call it _docsdir_.
+.. Download the javadoc artifact from the repository and copy it to
+.. Unzip it in _docsdir_.
+.. Do svn add on _docsdir_.
+.. Edit xdocs/javadoc.xml and add links to the new javadoc.
+. Build and test. Follow the instructions in site/HOWTO to push the site
+changes to the Apache web site.
+=== Post release modifications and documentation
+Follow this procedure if a significant bug is found or if the TCK must
+be modified because a test challenge is found to be valid.
+. Create a new branch from the release branch, incrementing the minor
+number. For example, create a branch named 2.1.1, from the 2.1 branch.
+. Merge bug fixes or other modifications into the new branch.
+. In the new branch, modify trunk/README.txt to include a section on bug
+fixes since the 2.1 release, and to suggest checking out the source from
+a bug-fix branch to get the fixes listed.
+. Link to this README in the web interface to svn from the .cgi download
+page and from http://db.apache.org/jdo/tck.html.

View raw message