Recent changes to ReleaseGuide

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Fri, 04 Apr 2014 12:11:09 -0000

--- v5
+++ v6
@@ -11,12 +11,12 @@
 - Update ./CHANGELOG and ./README.
 - Commit.
 - Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern tags/MAPGRAPH_RELEASE_X_Y_Z.
-- Create a new directory on sourceforge for the release [https://sourceforge.net/projects/mpgraph/files/]. Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
+- Create a new directory on sourceforge for the release . Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
 - Generate the release artifact (make release) and upload into the directory on sourceforge. Be sure to click on the "i" icon and specify the necessary metadata for each release file (sourceforge will not update the "release" until you do this). DO NOT RENAME THESE DEPLOYMENT FILES. The names you give to SF are the actual names for the downloaded files....

 PostConditions
 ---------
 - notify developers that the branch is open again.
-- blog it [http://www.bigdata.com/bigdata/blog/] and elsewhere.
+- blog it  and elsewhere.
 - post the release notes to the sourceforge project news (admin -> features -> news -> submit)
 - send out an email announcement (we maintain a mailing list).

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Fri, 04 Apr 2014 12:09:27 -0000

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Fri, 04 Apr 2014 12:08:57 -0000

--- v3
+++ v4
@@ -10,7 +10,7 @@
 - Bump the version in ./Makefile and ./doc/Doxyfile. 
 - Update ./CHANGELOG and ./README.
 - Commit.
-- Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern MPGRAPH_RELEASE_X_Y_Z.
+- Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern tags/MAPGRAPH_RELEASE_X_Y_Z.
 - Create a new directory on sourceforge for the release [https://sourceforge.net/projects/mpgraph/files/]. Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
 - Generate the release artifact (make release) and upload into the directory on sourceforge. Be sure to click on the "i" icon and specify the necessary metadata for each release file (sourceforge will not update the "release" until you do this). DO NOT RENAME THESE DEPLOYMENT FILES. The names you give to SF are the actual names for the downloaded files....

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Sat, 22 Mar 2014 20:20:59 -0000

--- v2
+++ v3
@@ -3,13 +3,12 @@
 - notify developers that we are closing the branch down for a release and wait for the all clear.
 - verify performance against standard benchmarks
 - verify CI builds.
-- update CHANGELOG and README.

 Release
 ---------
 - Ensure that the code builds and run the test suite.
 - Bump the version in ./Makefile and ./doc/Doxyfile. 
-- Edit ./CHANGELOG.
+- Update ./CHANGELOG and ./README.
 - Commit.
 - Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern MPGRAPH_RELEASE_X_Y_Z.
 - Create a new directory on sourceforge for the release [https://sourceforge.net/projects/mpgraph/files/]. Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Sat, 22 Mar 2014 20:16:51 -0000

--- v1
+++ v2
@@ -7,8 +7,11 @@

 Release
 ---------
+- Ensure that the code builds and run the test suite.
+- Bump the version in ./Makefile and ./doc/Doxyfile. 
+- Edit ./CHANGELOG.
+- Commit.
 - Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern MPGRAPH_RELEASE_X_Y_Z.
-- Make sure the TAG URL is reflected in the CHANGELOG.
 - Create a new directory on sourceforge for the release [https://sourceforge.net/projects/mpgraph/files/]. Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
 - Generate the release artifact (make release) and upload into the directory on sourceforge. Be sure to click on the "i" icon and specify the necessary metadata for each release file (sourceforge will not update the "release" until you do this). DO NOT RENAME THESE DEPLOYMENT FILES. The names you give to SF are the actual names for the downloaded files....

ReleaseGuide modified by Bryan Thompson

Bryan Thompson — Mon, 17 Feb 2014 22:00:50 -0000

PreConditions

notify developers that we are closing the branch down for a release and wait for the all clear.
verify performance against standard benchmarks
verify CI builds.
update CHANGELOG and README.

Release

Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern MPGRAPH_RELEASE_X_Y_Z.
Make sure the TAG URL is reflected in the CHANGELOG.
Create a new directory on sourceforge for the release [https://sourceforge.net/projects/mpgraph/files/]. Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
Generate the release artifact (make release) and upload into the directory on sourceforge. Be sure to click on the "i" icon and specify the necessary metadata for each release file (sourceforge will not update the "release" until you do this). DO NOT RENAME THESE DEPLOYMENT FILES. The names you give to SF are the actual names for the downloaded files....

PostConditions

notify developers that the branch is open again.
blog it [http://www.bigdata.com/bigdata/blog/] and elsewhere.
post the release notes to the sourceforge project news (admin -> features -> news -> submit)
send out an email announcement (we maintain a mailing list).