Re: The update stream, 3.4, 3.5, harvesting

Tim Rowledge wrote:
> 
> This is all good stuff and I want to offer my thanks to everyone that
> is working so hard on these matters.
> 
> I'd really appreciate an update to the sqfixes pages so that we can get
> to work on the stuff sitting around right now. Better tools for the
> future are important but we should try to get moving asap.

Okay, I've just put up some new harvesting tables on the sqfixes pages, so we can do some work now, for those interested.  28Jan03 is really the current table, but I also included one from last November, just in case there were some enhancements back then worth looking over.

See:

http://209.143.91.36/super/415

- Doug
From [email protected] Tue Feb 04 05:31:33 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 12729 invoked from network); 4 Feb 2003 05:31:32 -0000
Received: from mailhost2-sfldmi.sfldmi.ameritech.net (HELO
	mailhost.det3.ameritech.net) (206.141.193.106)
	by mail.theinternetone.net with SMTP; 4 Feb 2003 05:31:32 -0000
Received: from riskmetrics.com ([66.72.184.114])
	by mailhost.det3.ameritech.net
	(InterMail vM.4.01.02.17 201-229-119) with ESMTP
	<20030204053108.QIIH20886.mailhost.det3.ameritech.net@riskmetrics.com>
	for <[email protected]>;
	Tue, 4 Feb 2003 00:31:08 -0500
Date: Tue, 4 Feb 2003 00:27:54 -0500
Mime-Version: 1.0 (Apple Message framework v551)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Doug Way <[email protected]>
To: [email protected]
Content-Transfer-Encoding: 7bit
Message-Id: <[email protected]>
X-Mailer: Apple Mail (2.551)
Subject: [Squeakfoundation]3.4 release
X-BeenThere: [email protected]
X-Mailman-Version: 2.1
Precedence: list
Reply-To: Discussing the Squeak Foundation
	<[email protected]>
List-Id: Discussing the Squeak Foundation
 <squeakfoundation.lists.squeakfoundation.org>
List-Unsubscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=unsubscribe>
List-Archive: <http://lnx-12.ams-2.theinternetone.net/pipermail/squeakfoundation>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2003 05:31:33 -0000


As the new update stream guy (and, by association, the guy in charge of 
getting releases out the door), it's time to release Squeak 3.4!  
(Sorry for falling a few days behind on this.)

To help clarify the process for me and everyone else, I wanted to give 
a quick overview of the release timeline, to make sure I have the right 
idea.  Here are the steps:

1. Mark the image as 3.4 final, and upload a copy of the final image to 
the ftp site.  Immediately afterward, announce this to the squeak-dev 
list.
2. Within a few days (?), have the 3.4 VMs uploaded to the ftp site.  
This should include a Windows VM, a Mac (Carbon) VM, and the sources 
(?) for the Unix VM, and possibly at least one pre-built Unix VM.  
(Which one(s)?  Probably Linux at least.)  Also, pre-packaged 
zip/stuffit files containing the VM/image/changes/sources files should 
be made available on the ftp site for Windows & Mac.
3. Shortly afterward, the http://squeak.org download page should be 
updated so that it points to the 3.4 files instead of 3.2.
4. After that, the release of Squeak 3.4 can be announced to the rest 
of the world.  (Slashdot, etc.  See the External Relations SqF wiki 
page.)

Does this sound about right?

The only questions I have are:
- Should we wait a few days between steps 1 and 2?  This would let 
people test the final image a bit just to make sure there wasn't some 
major problem, and maybe check out any final cosmetic tweaks.  Also, it 
would give the VM maintainers a few days to get their VMs ready.  But 
perhaps this isn't necessary... maybe we should make sure the VMs are 
ready before we declare 3.4 final.  (Certainly they should be almost 
ready anyway.)
- Which Unix VMs should be available immediately upon the release of 
3.4?  Sources?  A Linux VM?  Debian and/or RPMs?  Obviously we don't 
want to wait around for lots of lesser-known Unix variant VMs to be 
compiled.  (PDA's and other platforms' VMs can be made available later, 
too.)

I think I have a good idea of who is responsible for most of the above. 
  Scott/myself for step 1, Andreas/John/Ian for providing the VMs, Bruce 
(or myself) for updating the ftp site and squeak.org site, and Cees for 
announcing to the rest of the world.  (Do we still need someone to 
create Debian/RPMs if we want those?)

Anyway, we should probably move ahead with step 1 in the next couple of 
days, but before doing this, I'll check with the VM maintainers & 
others to make sure we can move ahead with the rest of the steps.  Also 
need to look at the image tweaks that Tim mentioned a few days ago.

- Doug

(btw, thanks to Alejandro Magistrello for filling out the "already 
incorporated" items on the swiki harvesting tables)