river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tho...@apache.org
Subject svn commit: r1132560 - /river/site/trunk/content/building-a-release.mdtext
Date Mon, 06 Jun 2011 09:38:10 GMT
Author: thobbs
Date: Mon Jun  6 09:38:10 2011
New Revision: 1132560

URL: http://svn.apache.org/viewvc?rev=1132560&view=rev
Log:
Added release notes info

Modified:
    river/site/trunk/content/building-a-release.mdtext

Modified: river/site/trunk/content/building-a-release.mdtext
URL: http://svn.apache.org/viewvc/river/site/trunk/content/building-a-release.mdtext?rev=1132560&r1=1132559&r2=1132560&view=diff
==============================================================================
--- river/site/trunk/content/building-a-release.mdtext (original)
+++ river/site/trunk/content/building-a-release.mdtext Mon Jun  6 09:38:10 2011
@@ -34,6 +34,27 @@ Add your key to the KEYS file in the rep
  * River-trunk should run successful.
  * River-verify should run successful. (not yet?)
 
+## Gather Release Notes From Jira
+
+First [manage the versions][5] of River using Jira.  Make sure there is an appropriate release
that Jira issues are have been assigned to.  You can then view the [Roadmap][4] screen in
Jira to create the release and make sure that the correct Jira issues are associated to it.
+
+Move the Jira issues around appropriately, especially if you're releasing before all the
issues have been resolves.  In this case, you need to postpone the remaining issues until
a later release.
+
+You can then use Jira to generate the release notes.  This is done Road Map --> Release
--> Summary --> Release Notes (next to "Filters").
+
+The release notes need to be pasted into;
+
+    river/trunk/src-doc/static/release-notes/index.html
+
+## Update Version Numbers
+
+There are version numbers in the following places that need to be updated with the new release
number/name.
+
+  - com.sun.jini.constants.VersionConstants.java (SERVER_VERSION)
+  - river/trunk/src-doc/static/release-notes/index.html (version number)
+
+In the above HTML page, there is also a section on "changes by component" which should also
be updated.  This should be easy to do by referring to the Jira-generated release notes.
+
 ## Branch the repository
 
     svn cp https://svn.apache.org/repos/asf/river/jtsk/trunk https://svn.apache.org/repos/asf/river/jtsk/branches/$VERSION
@@ -42,10 +63,6 @@ Add your key to the KEYS file in the rep
 
     svn cp https://svn.apache.org/repos/asf/river/jtsk/trunk https://svn.apache.org/repos/asf/river/jtsk/tags/$VERSION
 
-## Gather Release Notes From Jira
-
-...
-
 ## Build the release products
 
     ant -Dversion=$VERSION clean release
@@ -94,4 +111,6 @@ Add your key to the KEYS file in the rep
 
   [1]: http://www.apache.org/dev/release-signing.htm
   [2]: http://www.apache.org/dev/release-signing.html#sign-release
-  [3]: http://www.apache.org/dev/release-signing.html#sha-checksum
\ No newline at end of file
+  [3]: http://www.apache.org/dev/release-signing.html#sha-checksum
+  [4]: https://issues.apache.org/jira/browse/RIVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
+  [5]: https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310600
\ No newline at end of file



Mime
View raw message