We have shortened the beta/gamma stages by quite a bit more than we
planned. I think before we proceed, we should make sure we are ready.

I see 3 issues that might make this release more buggy than previous
releases, which I think is unacceptable.
1. Have the debugger/context issues stabilized enough to go gamma?
2. Have we fixed all the calls to deprecated stuff made in the image?
3. Do we have a clear idea about how users of this release will be able
to work at least as well as with the previous scheme of Full releases?
IOW:
- is SM1.1 ready so that we can split the current version of each
package? if not, 
- are all the packages that have been removed in such a state that we
can pull them in as they are now and thus release a Full image that will
work?

There may be other issues, those are the ones I could think of. Unless
we're quite sure that in each of these we have a clear solution that is
better than 3.5 provides, I think we should delay the move to gamma.

Either way, the time between now and release is quite short, and 3.6
won't change much before the release. This is a good moment for everyone
that might still be doing development in something other than the latest
to upgrade and help with the testing. What we don't catch before the
release will cause us much more trouble than if we catch it while in
beta. 

Daniel

Doug Way <dway at riskmetrics.com> wrote:
> 
> Here's the final SARInstaller update for 3.6, plus one other fix which 
> was approved in the last day.
> 
> There will probably be only one more round of fixes in the next day or 
> two for 3.6beta (if needed), before we move to gamma.  3.7alpha will be 
> opened at the same time.
> 
> - Doug Way
> 
> 
> ------------------------------
> 
> 5372SARInstallerFor36-16c -- Ned Konz -- 21 July 2003
> 22 July
> fixed postscript
> 21 July (v16)
> Packaged as a separate package (identical to the v16 version of the 
> SARInstaller for 3.4) with only SARInstaller methods.
> Added SqueakMap magic in postscript.
> Fixed a bug in the DVS file-in.
> 5 July:
> Adds a default (DWIM) mode in which SAR files that are missing both a 
> preamble and postscript have all their members loaded in a default 
> manner.
> Changes the behavior of #extractMemberWithoutPath: to use the same 
> directory as the SAR itself.
> Added #extractMemberWithoutPath:inDirectory:
> Moved several change set methods to the class side.
> Made change set methods work with 3.5 or 3.6a/b
> Now supports the following file types:
> Projects (with or without construction of a ViewMorph)
> Genie gesture dictionaries
> Change sets
> DVS packages
> Monticello packages
> Graphics files (loaded as SketchMorphs)
> Text files (loaded as text editor windows)
> Morph(s) in files
> Now keeps track of installed members.
> 
> 5373urlWithPassword-ls -- Lex Spoon -- 15 June 2003
> removed testcases (v5, approved)
> Parse URL's that have a password specified in them.
> Adds test cases for this situation in the UrlTestCase classe; if there 
> is a package somewhere that has URL tests in it, these should be moved 
> there.
> Also does some minor refactoring of the relevant code.
> The current code gives a walkback on encountering such URL's, which is 
> frustrating if you are trying to delete spams within Celeste.
> Note: this code does not actually *use* the username and password that 
> are specified; it only parses them.