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 "ReleasePublication" by RichardHillegas
Date Tue, 14 Dec 2010 17:44:17 GMT
Dear Wiki user,

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

The "ReleasePublication" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/ReleasePublication?action=diff&rev1=12&rev2=13

--------------------------------------------------

  
    {X} If the update doesn't get generated within a day or two, send email to derby-dev@db.apache.org
letting them know you updated the file and that the update appears to be delayed (site-dev@apache.org
needs to be notified). If you have to post to site-dev@apache.org, make sure that you are
subscribed to that list--your question will be answered there and you won't be able to look
it up later because that list is not archived publicly.
  
+  1. Circulate a release announcement to derby-dev.
-  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 (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 your Apache account!
  
    Include a description of the project, and a description of any significant new features
or important bug fixes. 
  
@@ -286, +282 @@

   1. Wire the new release into the upgrade tests.
  
    Add the new release to the OLD_VERSIONS table in org.apache.derbyTesting.functionTests.tests.upgradeTests.!OldVersions.

+ 
+  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.

+ 
+   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.
+ 
+   Update STATUS to reflect that the release has occurred. Check in the new file. 
+ 
+  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 (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.
+ 
+   <!> Send the text which the community reviewed above. Note that you can only send
emails to announce@apache.org from your Apache account!
  
   1. Update the News section of the website.
  
@@ -305, +322 @@

  
    Update any information about new and upcoming releases (for new releases link to the download
page) on the wiki's FrontPage.
  
-  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.

- 
-   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.
- 
-   Update STATUS to reflect that the release has occurred. Check in the new file. 
  
  
  You're done!

Mime
View raw message