[etoys-dev] [SVN][1680] Release-HowTo.txt: Minor improvements
commits at etoys.squeak.org
commits at etoys.squeak.org
Sun Jun 24 19:21:25 EDT 2012
Repository: http://etoys.squeak.org/svn
Revision: 1680
Author: bf
Date: 2012-06-24 23:21:22 +0000 (Sun, 24 Jun 2012)
Log Message:
-----------
Release-HowTo.txt: Minor improvements
Modified Paths:
--------------
trunk/Documentation/Release-HowTo.txt
-------------- next part --------------
Modified: trunk/Documentation/Release-HowTo.txt
===================================================================
--- trunk/Documentation/Release-HowTo.txt 2012-06-24 22:52:04 UTC (rev 1679)
+++ trunk/Documentation/Release-HowTo.txt 2012-06-24 23:21:22 UTC (rev 1680)
@@ -69,24 +69,25 @@
1. use the latest released version (e.g., a clean Etoys-To-Go)
2. load updates, say yes to load the latest package versions
-3. in Monticello, browse the latest config, e.g. "update-bf.16"
+3. in Monticello, browse the latest config (e.g. "update-bf.16") in the
+ "etoys" repository ( http://source.squeak.org/etoys )
4. in the MC Config browser, choose "update from image". This will
record the updated versions in the config
-5. store the config in the local "etoys" repo, giving it a
- new version name, e.g. "update-bf.17"
+5. store the config in the "etoys" repo, giving it a new version name,
+ e.g. "update-bf.17"
6. display the change log from the previous config to this one:
`Utilities defaultRepositoryChangeLogOn: Transcript`
7. create a new change set, naming it after the repo version shown at
the top of the change log, e.g. "repo3456-bf"
8. paste the change log into the change set preamble, be careful to
replace all double quotes since this is a Smalltalk comment
-9. create the Postscript loading the config map as in the example
+9. add a Postscript loading the config map as in the example
above. I usually copy the old postscript, delete the old package
list, and paste in the new one from the config just stored.
(for easier copy-and-paste, store the config map in the local
package cache)
-10. save the change set, and broadcast it to the update stream using
- the FileList tool.
+10. file-out the change set, and broadcast it to the update stream
+ using the FileList tool.
This takes less than 10 minutes, as this screencast demonstrates:
@@ -182,13 +183,14 @@
switches the update stream, it corresponds to the "#" sections in
http://etoys.squeak.org/updates/updates.list
* Save and quit the image
-* for testing, do _not_ run the image from here, because this will
+* For testing, do _not_ run the image from here, because this will
modify at least the changes file. Better to build a new Etoys-To-Go
(see "installers" section below) or make a copy elsewhere.
* The release builder generated new translation template files (*.pot)
- in the Etoys project directory. Move them to po/templates
-* commit image, changes, and pot files to svn, mention the version and
- update number in the commit message
+ in the Etoys project directory. Move them to po/templates
+* Update the NEWS file
+* Commit image, changes, NEWS, and pot files to svn, mention the
+ version and update number in the commit message
This is also demonstrated in this screencast:
More information about the etoys-dev
mailing list