forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r358322 - /forrest/trunk/plugins/RELEASE_PROCESS.txt
Date Wed, 21 Dec 2005 16:51:40 GMT
Author: rgardler
Date: Wed Dec 21 08:51:34 2005
New Revision: 358322

add a note about when to update minimum forrest version and mention the new 'release' target


Modified: forrest/trunk/plugins/RELEASE_PROCESS.txt
--- forrest/trunk/plugins/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/plugins/RELEASE_PROCESS.txt Wed Dec 21 08:51:34 2005
@@ -33,6 +33,10 @@
 by doing 'tools/ant/bin/ant deploy' [1]. The build system will take care of
 everything else for you.
+Deployment is carried out with the command "ant deploy". Since this does not
+affect releaed versions of the plugin it can be run at any time (note some minimal 
+tests are done during the deploy process). 
 [1] See the note about using our own version of Ant:
@@ -47,6 +51,24 @@
 Once the deployment is complete the version number should be increased and the 
 '-dev' postfix will be appended.
+To release a plugin one should run the command "ant release", however, there is 
+more to it than this.
 TODO: announcement emails
 TODO: tagging source tree
+What if a new feature breaks compatability with a released version of Forrest?
+If you add a feature to a plugin that will break compatability with a released version of
+Forrest then you should up the forrest version number in the plugins build.xml file. This
+will prevent the new version of the plugin being made avialble to the older version of 
+However, you might light to consider doing a release of the plugin before you break 
+compatability. It depends on what other changes there are to the plugin before you
+start your work. It is always best to raise this on the dev list.

View raw message