[etoys-dev] [SVN][1101] Add version number discussion to Release-HowTo.

[commits at etoys.squeak.org]

Repository: http://etoys.squeak.org/svn

Revision: 1101
Author:   bf
Date:     2012-03-03 14:15:53 +0000 (Sat, 03 Mar 2012)
Log Message:
-----------
Add version number discussion to Release-HowTo.

Modified Paths:
--------------
    trunk/Documentation/Release-HowTo.txt

-------------- next part --------------
Modified: trunk/Documentation/Release-HowTo.txt
===================================================================
--- trunk/Documentation/Release-HowTo.txt	2012-03-01 07:08:43 UTC (rev 1100)
+++ trunk/Documentation/Release-HowTo.txt	2012-03-03 14:15:53 UTC (rev 1101)
@@ -25,7 +25,7 @@
 called "Miscellaneous files" at the end of this document which gives
 details on some particular files like example projects and QuickGuides.
 
-1. Prepare an update 
+1. The update stream
 --------------------
 
 The package versions for any (alpha/beta/final) Etoys release are fixed
@@ -33,6 +33,31 @@
 
     http://etoys.squeak.org/updates/
 
+### Version numbers ###
+
+The update stream is organized by versions. Different updates can be
+pushed for different versions, but we do not currently make use of that
+feature. The versions are visible in the updates.list file:
+
+	http://etoys.squeak.org/updates/updates.list
+
+When switching to a new version number (but not for alpha/beta), you 
+need to put a changeset in the update stream to advance the version. It
+can either be unconditional (e.g. 4.1 to 4.1.1) or conditional like
+this one:
+
+	http://etoys.squeak.org/updates/2342jumpTo4dot1-bf.cs
+
+Do this at the beginning of a new release cycle.
+
+### Prepare an update ###
+
+To make sure what goes into a release and what not, we do not just use
+the latest packages from the repository, as during normal development.
+Instead, a config map with exact versions is pushed to the update
+stream. Then when you update the image and say "no" to load the latest
+packages you will get a repeatable configuration.
+
 This change-set does not actually containing changes, but loads a
 Monticello configuration map as a Postscript. It can, however, also
 contain "do-its" for house-keeping (though this is rarely needed). Here