db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by AndrewMcIntyre
Date Sat, 24 Sep 2005 00:12:28 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by AndrewMcIntyre:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

New page:
== Snapshots ==
 1. Run the snapshot target.

 At the top of your subversion view of the trunk or one of the branches, do:

 {{{svn up
ant -Dsane=false snapshot}}}

 It is best to do this in a view where there are no modified files or mixed revisions. This
will create a snapshot directory at the top level, which will contain the three snapshot files:

  * db-derby-[version]-[changenumber].tar.gz
  * db-derby-[version]-[changenumber].zip
  * derby_core_plugin_[version]_[changenumber].zip

 1.#2 Update the website.

 For instructions on how to build the website using Forrest, please see:

 http://db.apache.org/derby/papers/derby_web.html

  a. Place the three files created by the snapshot target into the src/documentation/content/xdocs/binaries
directory of the location to which you checked out the website source. 'svn add' them, and
'svn delete' any old snapshot that the new snapshot is replacing.

 b. Update the derby_downloads.xml page in the src/documentation/content/xdocs directory so
that the links to the current snapshot point to your new files.

 c. Run 'forrest site' at the top of the site tree.

 d. Check the changes. If they look good, 'svn commit' them. NOTE: you should revert any changed
files in build/tmp or build/site/skin.

 e. Update the website on svn.apache.org by logging into the machine and doing:

 {{{cd /www/db.apache.org/derby
svn up}}}

 The public Derby website updates roughly every two hours. Check that the site has updated
properly after that amount of time has passed.

 1.#3 Bump the version number.

 In the tools/release directory, run the Ant bumplastdigit target.

 {{{cd tools/release
ant bumplastdigit}}}

 This target updates tools/ant/properties/release.properties and several test canons that
contain the version number. Check that the version number is correct.

Releases
1. Announce your intention to have a release on the list
2. Volunteer (or enlist) a release manager
3. Make sure that an entry for the release version exists in JIRA
4. For a bug fix release, target the bugs you feel should be fixed in JIRA
5. Fix the bugs, update STATUS and CHANGES as needed
6. Create the release distributions and checksums, sign the distributions
6a. Put your key in KEYS if you haven't done so.
6b. Verify checksums/signatures
7. Post the distributions
8. Vote on the distributions
9. Put distributions onto mirrors
9a. link -current to new files, move old files to archive
10. Create a page for the release, build/update site
12. Make everyone happy - create Eclipse plugins, deploy to Maven repository
11. Announce
13. Update STATUS again
14. Bump the version number to next version

Mime
View raw message