<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear 3dot10ees.<br>
<br>
re: 3.10 process, and 3.9.1 process.<br>
<br>
In collaboration with Edgar I have started an experimental process
which I hope will be useful for working collaboratively to generate
v3.10<br>
<br>
Here is an example of existing functionality. You can try this at a
command line near you:<br>
<br>
# squeak Squeak3.9-final-7067.image
<a class="moz-txt-link-freetext" href="http://installer.pbwiki.com/f/installer.st">http://installer.pbwiki.com/f/installer.st</a>
path=<a class="moz-txt-link-freetext" href="http://squeak310.pbwiki.com/">http://squeak310.pbwiki.com/</a> in=From39To310 done=save&quit<br>
<br>
This starts squeak with the 3.9 image, loading Installer as the startup
document, installer uses the scripts, beginning at
<a class="moz-txt-link-freetext" href="http://squeak310.pbwiki.com/From39To310">http://squeak310.pbwiki.com/From39To310</a> to upgrade. When everything is
complete the image is automatically saved.<br>
<br>
You can also try "in=From39To391".<br>
<br>
Here is a relatively advanced example of how a developer might use it
(the testing part is still to do):<br>
<br>
The following command line, starts squeak with the current release
image. It then loads Installer as the startup document, and Installer
is instructed to upgrade From39To310. In performing this upgrade it
will obtain the scripts for each step following a search path. In this
case I have specified Instructions from my locally served txt files
first, the development (unstable) branch second, or the release
(stable) branch last. [up to this point is working] Once the install is
complete, control is passed on to TestRunner, who runs all the usual
tests. When the tests are complete the image is saved.<br>
<br>
# squeak Squeak3.9-final-7067.image
<a class="moz-txt-link-freetext" href="http://installer.pbwiki.com/f/installer.st">http://installer.pbwiki.com/f/installer.st</a>
path=<a class="moz-txt-link-freetext" href="http://localhost/squeak310/*.txt;http://squeak310.pbwiki.com/*-dev;http://squeak310.pbwiki.com/">http://localhost/squeak310/*.txt;http://squeak310.pbwiki.com/*-dev;http://squeak310.pbwiki.com/</a><br>
in=From39To310 next=TestRunner testsuites=allStandardTests
reject=toDo;expectedFailures testlog=test.out done=save.<br>
<br>
For creating a 'stable' version instead, the additional search path
options are omitted and control is handed over to the 'TidyUp' script
which removes the tests, and test tools before saving. e.g.
"path=squeak310.pbwiki.com/ next=TidyUp done=save&quit".<br>
<br>
While many of the details of 3.10 process have yet to be fleshed out. I
defined 'From39To391' as the first step. I do not know what the
existing process for 3.9.1 is, or whether there is one yet, but if you
look on <a class="moz-txt-link-freetext" href="http://squeak310.pbwiki.com/From39To391">http://squeak310.pbwiki.com/From39To391</a> here we have in place a
potential mechanism for harvesting and testing fixes from mantis in a
collaborative manner. (can anyone tell me how the update stream works
and whether it could be automatically generated from these scripts?)<br>
<br>
To nominate a fix for harvesting from mantis, edit the page
From39To391MantisFixes-dev, and add a snippet like so:<br>
<br>
<blockquote>---<br>
</blockquote>
<blockquote>**category:** Squeak-Collections minor **author:**
[renggli] (needs test?)<br>
Prints wide-character using the safe form: (Character value: xxxx)
rather than $ <br>
<code st><br>
Installer mantis fixBug: 5700.
"[<a class="moz-txt-link-freetext" href="http://bugs.impara.de/view.php?id=5700">http://bugs.impara.de/view.php?id=5700</a>|String-storeOn: to handle wide
chars safely]"<br>
</code st><br>
</blockquote>
<br>
This bug report on mantis has also been prepared for harvesting by
appending a script as a note to the bug report (the last such script on
the page is the one that Installer will use). The script nominates
which of the uploaded files are to be loaded for applying the fix, and
which are to be loaded to obtain test cases for the fix. e.g.<br>
<br>
<blockquote> "fix begin"<br>
Installer mantis bug: 5700 fix: 'Character-storeOn.st'. <br>
"fix test"<br>
Installer mantis bug: 5700 fix: 'Character-storeOn-testneeded.st'<br>
"fix end"<br>
</blockquote>
<br>
I have set up notifications for changes to these scripts on the wiki to
be automatically be sent to the v3dot10 mailing list, on a daily basis.
<br>
<br>
thoughts, objections, and any feedback would be most welcome<br>
<br>
best regards<br>
<br>
Keith<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>