From jdo-commits-return-2457-apmail-db-jdo-commits-archive=www.apache.org@db.apache.org Fri Aug 29 23:22:49 2008 Return-Path: Delivered-To: apmail-db-jdo-commits-archive@www.apache.org Received: (qmail 98508 invoked from network); 29 Aug 2008 23:22:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2008 23:22:45 -0000 Received: (qmail 84237 invoked by uid 500); 29 Aug 2008 23:22:44 -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 84228 invoked by uid 99); 29 Aug 2008 23:22:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2008 16:22:44 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2008 23:21:54 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 413342388986; Fri, 29 Aug 2008 16:21:55 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r690419 - /db/jdo/HowToReleaseJDO.html Date: Fri, 29 Aug 2008 23:21:55 -0000 To: jdo-commits@db.apache.org From: mcaisse@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20080829232155.413342388986@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: mcaisse Date: Fri Aug 29 16:21:54 2008 New Revision: 690419 URL: http://svn.apache.org/viewvc?rev=690419&view=rev Log: Modifications to site section. Modified: db/jdo/HowToReleaseJDO.html Modified: db/jdo/HowToReleaseJDO.html URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=690419&r1=690418&r2=690419&view=diff ============================================================================== --- db/jdo/HowToReleaseJDO.html (original) +++ db/jdo/HowToReleaseJDO.html Fri Aug 29 16:21:54 2008 @@ -208,7 +208,7 @@
 ssh people.apache.org
 cp -r public_html/dist/db /www/www.apache.org
-cp -r public_html/dist/m1-ibiblio-rsync-repository /www/people.apache.org/repo
+cp -r public_html/dist/m1-ibiblio-rsync-repository/* /www/people.apache.org/repo/m1-ibiblio-rsync-repository
 
NOTE!! Be sure that there is no slash at the end of the directory you are copying from; otherwise the files will be put in the wrong target directory. @@ -229,7 +229,7 @@
  1. Update the Apache JDO web site to point the downloads page to the release.
      -
    1. In site/xdocs/releases create release-2.n.html.
    2. +
    3. In site/docs/releases create release-2.n.html. Edit the release numbers
    4. In site/docs/releases create release-2.n.cgi. The .cgi file contents are identical to the other .cgi files in the release directory; only the file name differs.
    5. Edit site/xdocs/downloads.xml to link to the new release page .cgi document.
    6. Build and test as described in the site/HOWTO document.
    7. @@ -237,8 +237,8 @@
       svn add xdocs/releases/release-2.n.html 
       svn add docs/releases/release-2.n.html 
      +svn add xocs/releases/release-2.n.cgi 
       svn add docs/releases/release-2.n.cgi 
      -svn commit
       
    8. Set the svn properties svn:eol-style to native and svn:executable to true for the .cgi files.
    9. @@ -247,7 +247,6 @@
    10. Change the link to RunRules on the TCK page to link to the RunRules.html file of the latest release.
    11. Update the news list on the site home page to announce the new release. -Build, test, and push as described in HOWTO.
    12. Add the javadoc for the release to the site.
        @@ -258,7 +257,7 @@
      1. Edit xdocs/javadoc.xml and add links to the new javadoc.
    13. -
    14. Follow the instructions in site/HOWTO to push the site changes to the Apache web site.
    15. +
    16. Build and test. Follow the instructions in site/HOWTO to push the site changes to the Apache web site.

    Preparation for the next release

    In trunk, update version numbers for the next spec or major release. See the instruction under Detailed process steps.