Page History

...

• openjpa-projects/CHANGES.txt
  1. Update the overview paragraph with the new version and a brief description of the release.
  2. Remove the previous changes section and replace with a url to the location in SVN. This is similar to what HTTPD does in its CHANGES file
  3. Create a new section : OpenJPA x.y.z changes and copy the JIRA issues resolved in this section. You may want to do some minor editing by hand to ensure the file respects the 80 character column width guideline.
  4. commit the changes back to svn
• openjpa-project/RELEASE-NOTES.html
  1. Similar to CHANGES.txt you need to update the version number and provide a brief description of the release.
  2. Remove the previous list of changes for the previous release. Replace this with a link to the last release's file in SVN.
  3. Add a new section. This can be copied from the JIRA page with one exception (see the next step).
  4. Update the links at the top of the file. If you've copied changes from JIRA you'll see a section like this :

     Code Block
     <h2> Bug </h2>

     Replace it with

     Code Block
     <h2><a name='Bug'> Bug </h2>

     You should also check the links at the top to make sure they are all valid.
• openjpa-project/NOTICE.txt
  NOTICE.txt "usually" does not need to be updated. The exceptions are when a new dependency has been introduced (ie a new version of Serp) or if a new source file containing a copyright notice is introduced.
• openjpa-project/LICENSE.txt
  Similar to NOTICE.txt this file does not require updating in each release. It should contain the current version of the Apache license, and any other licenses mentioned in NOTICE.txt.
• openjpa-project/README.txt
  This file rarely needs updating - just make sure the URL is accurate.
• openjpa-project/BUILDING.txt
  This file rarely needs updating.