Re: [BUG?]Upgrading 3.2 to 3.3alpha

"Roger Vossler" <rvossler@xxxxxxxxx> asked...

>I thought that Squeak Central was in control of the update process. Who 
>exactly is the maintainer
>of the 3.2 fork and why did this fork take place? Is Squeak Central now out of 
>the loop?

Hi, Roger -

Sorry about the misleading use of words.  That maintainer was me.  I had 
originally worded my reply as though Andrew had been maintaining his own image, 
and it said something like "you chose NO".  Then I realized this is the case 
for any 3.2, so I changed it to this impersonal reference to the election of 
the fork to 3.2 in update 4653.

And to answer the bigger question, no, SQC is not out of the loop (as far as we 
know ;-).  On the contrary I expect various of us to be more active again as we 
get into the fall.  I'll try to write down my thoughts about some of the 
current activities and how they might play together in a coherent manner as we 
go forward.

        - Dan
--------------------------
>On Friday, August 30, 2002, at 07:57 PM, Dan Ingalls wrote:
>
>>"Andrew C. Greenberg" <werdna@xxxxxxxxx>  asked...
>>
>>>I seem to be unable to upgrade the most current published version of Squeak 
>>>3.2 to 3.3.  Am I missing something?
>>
>>Yes.
>>
>>>     1. Take a raw 3.2 image
>>>     2. DoIt:  "SqueakVersion setImage"
>>>     3. Help -> updates
>>>
>>>This loads a few updates, but then stops on or about update 4681.
>>>
>>>Please advise where I am missing the boat, or what I should do to effect the 
>>>update to current alpha using the updaters.
>>
>>A choice was offered, at update #4653, to advance to 3.3 and the maintainer 
>>of the 3.2 fork chose NO.  There are no provisions for advancing to 3.3 after 
>>that point.
>>
>>It's true that this differs from most earlier releases, because 3.2 continued 
>>to evolve after the fork, rather than merely receiving a few fixes that might 
>>have allowed for later advancing to 3.3.
>>
>>It is conceivable that you could fool your system into thinking that it was 
>>at update 4653 (remove or rename all changeSets after this #), *then* change 
>>your version and go forward from there, but I have no certainty that it would 
>>be successful.
>>
>>Hope this helps.
>>
>>      - Dan