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 DyreTjeldvoll
Date Thu, 01 May 2008 19:07:42 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 DyreTjeldvoll:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  
   1. Announce the release.
  
-   Twenty-four hours after putting the release files in the mirror directory, verify that
you can reach them through a mirror. Then, you should email derby-dev, derby-user, general@db.apache.org,
announce@apache.org and anyone else you think might be interested an announcement concerning
the release. See past release announcements for examples.
+   Twenty-four hours after putting the release files in the mirror directory, verify that
you can reach them through a mirror (the mirroring will likely take effect long before this).
Then, you should email derby-dev, derby-user, general@db.apache.org, announce@apache.org and
anyone else you think might be interested an announcement concerning the release. See past
release announcements for examples.
  
+   <!> Note that you can only send emails to announce@apache.org from Apache account!
+ 
+   Include a description of the project, and a description of any significant new features
or important bug fixes. 
+ 
-   Include a description of the project, and a description of any significant new features
or important bug fixes. Every tech news blog remotely related to Java or databases will pick
up the announcement and post it verbatim, so it's a good idea to spell check it, proofread
it a couple of times, and/or get input from derby-dev on its content.
+   (!) Every tech news blog remotely related to Java or databases will pick up the announcement
and post it verbatim, so it's a good idea to spell check it, proofread it a couple of times,
and/or get input from derby-dev on its content.
  
   1. Tag the release in subversion.
  
@@ -681, +685 @@

    Update the News section at the bottom of the front page of the Derby website. Add the
announcement mail to the top of the news items at http://db.apache.org/derby/index.html#News

  
   1. Update JIRA versions and merge development versions into released version.
+  
+   a. Mark the release id as a released version in JIRA.
+    * Go to the Administration page, select Derby, then click the Manage versions link on
the bottom right. 
+    * Click the Release link next to the version id of the release and add the release date.
In addition, you may need to create a new version id for the next release vehicle on the branch.

  
-   Mark the release id as a released version in JIRA. To do this, go to the Administration
page, select Derby, then click the Manage versions link on the bottom right. Click the Release
link next to the version id of the release and add the release date. In addition, you may
need to create a new version id for the next release vehicle on the branch. The older development
versions used for tracking changes between releases are no longer needed, and old versions
should be merged into the release version. E.g. for the 10.3.1.4 release, 10.3.0.0, 10.3.1.0,
10.3.1.1, 10.3.1.2, and 10.3.1.3 need to be merged into the released 10.3.1.4. Click the Merge
button next to the oldest release. Select all the versions in the list on the right to merge
and then the released version to merge to on the left (in the example above, this would be
10.3.1.4), and click the Merge button and confirm the merge.
+   a. The older development versions used for tracking changes between releases are no longer
needed, and old versions should be merged into the release version. E.g. for the 10.3.1.4
release, 10.3.0.0, 10.3.1.0, 10.3.1.1, 10.3.1.2, and 10.3.1.3 need to be merged into the released
10.3.1.4.
+    * Click the Merge button next to the oldest release. 
+    * Select all the versions in the list on the right to merge and then the released version
to merge to on the left (in the example above, this would be 10.3.1.4
+    * Click the Merge button and confirm the merge.
  
   1. Update STATUS again.
  

Mime
View raw message