[JDO-585] Process for providing post-release notes for tck users

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JDO 2 maintenance release 1 (2.1), JDO 2 maintenance release 2 (2.2), JDO TCK challenge fixes
• Fix Version/s: JDO 2 maintenance release 1 update 1 (2.1.1), JDO 2 maintenance release 2 (2.2)
• Component/s: tck, tck2-legacy
• Assignee: Michelle Caisse
• Reporter: Michelle Caisse
• Created: 21/Mar/08 17:53
• Updated: 02/May/13 02:29
• Resolved: 15/Aug/08 17:03

Description

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.

Issue Links

• is depended upon by: JDO-593 Cleanup glassfish entry in maven.repo.remote property