Return-Path: X-Original-To: apmail-db-jdo-commits-archive@www.apache.org Delivered-To: apmail-db-jdo-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4B0D717BA9 for ; Fri, 27 Feb 2015 17:49:29 +0000 (UTC) Received: (qmail 61422 invoked by uid 500); 27 Feb 2015 17:49:19 -0000 Mailing-List: contact jdo-commits-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-commits@db.apache.org Received: (qmail 61408 invoked by uid 99); 27 Feb 2015 17:49:19 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 17:49:19 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id AA761AC006C for ; Fri, 27 Feb 2015 17:49:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1662765 - /db/jdo/HowToReleaseJDO.html Date: Fri, 27 Feb 2015 17:49:19 -0000 To: jdo-commits@db.apache.org From: mbo@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150227174919.AA761AC006C@hades.apache.org> Author: mbo Date: Fri Feb 27 17:49:19 2015 New Revision: 1662765 URL: http://svn.apache.org/r1662765 Log: Fix href link Modified: db/jdo/HowToReleaseJDO.html Modified: db/jdo/HowToReleaseJDO.html URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=1662765&r1=1662764&r2=1662765&view=diff ============================================================================== --- db/jdo/HowToReleaseJDO.html (original) +++ db/jdo/HowToReleaseJDO.html Fri Feb 27 17:49:19 2015 @@ -111,8 +111,8 @@ https://svn.apache.org/repos/asf/db/jdo/
Update version number
-
  • Follow the instructions at Publishing Maven Artifacts to set up your development environment. +
  • Follow the instructions at + Publishing 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 @@ -125,9 +125,8 @@ https://svn.apache.org/repos/asf/db/jdo/ This creates the .jar and .pom files in the target directory of each subproject.
  • -
  • Run RAT, which is at http://creadur.apache.org/rat/, - on the release.
  • +
  • Run RAT, which is at + http://creadur.apache.org/rat/, on the release.
  • Do a dry run prepare and deployment of a snapshot release. @@ -137,7 +136,8 @@ https://svn.apache.org/repos/asf/db/jdo/ mvn deploy -Papache-release - Check the artifacts at the Maven release repository + Check the artifacts at + 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. @@ -167,8 +167,7 @@ mvn release:perform -Papache-release 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 + follow the instructions at Releasing a Staging Repository to release the artifacts.
  • Update the distribution repository at http://apache.org/dist/db/jdo/ @@ -218,9 +217,8 @@ svn add site/docs/releases/release-N. svn:executable to true for the .cgi files.
  • -
  • Change the link to RunRules on the TCK page to link - to the RunRules.html file of the latest release.
  • +
  • Change the link to RunRules on the 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 release.
  • Update the specification page to link to the new specification