From jdo-dev-return-7397-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Fri Jun 27 19:02:08 2008 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 4524 invoked from network); 27 Jun 2008 19:02:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2008 19:02:08 -0000 Received: (qmail 61707 invoked by uid 500); 27 Jun 2008 19:02:09 -0000 Mailing-List: contact jdo-dev-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-dev@db.apache.org Received: (qmail 61696 invoked by uid 99); 27 Jun 2008 19:02:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2008 12:02:09 -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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2008 19:01:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 630E3234C14F for ; Fri, 27 Jun 2008 12:01:47 -0700 (PDT) Message-ID: <1326809162.1214593307404.JavaMail.jira@brutus> Date: Fri, 27 Jun 2008 12:01:47 -0700 (PDT) From: "Michelle Caisse (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Commented: (JDO-585) Process for providing post-release notes for tck users In-Reply-To: <627914122.1206122125005.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608885#action_12608885 ] Michelle Caisse commented on JDO-585: ------------------------------------- Checked in updated versions of HowToReleaseJDO.html and README.html. revision: 672352 > Process for providing post-release notes for tck users > ------------------------------------------------------ > > Key: JDO-585 > URL: https://issues.apache.org/jira/browse/JDO-585 > Project: JDO > Issue Type: Improvement > Components: tck2, tck2-legacy > Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes > Reporter: Michelle Caisse > Assignee: Michelle Caisse > Priority: Minor > Fix For: JDO 2 maintenance release 2 > > Attachments: HowToReleaseJDO.html, README.html > > > There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line). > Each branch has its own version of README.txt. When a maintenance release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.