Re: re: Outstanding 3.4 bugs?

What I'm getting at here is that we have some fixes backlogged, which it
would be nice to get out into a release faster than the usual. I mean
mostly the one that has project saving broken, and a few more.

Also, it would be good, IMO, to exercise the process a bit more. Doug
just did it the first time, maybe doing it again would let us know what
takes time about it, what can be streamlined, what can be automated. 

It doesn't mean we have to commit to a 1 month release, and it doesn't
mean that very many things have to go in. Since few things will change,
there's less of a need for general exercising of the image, it's more
important to make sure that the fixes get reviewed and tested properly.
Which is also something we should improve, in order to speed up
harvesting.

I agree that stating "To get into 3.5, it has to posted, reviewed and
tested by 2 independent Squeakers that know whereof they speak, before
week n" will probably help. The remaining alpha time can be used to deal
with the integration.

I don't know how much time it'll take, let's just try to keep it light
and quick.

Daniel

Tim Rowledge <[email protected]> wrote:
> Daniel Vainsencher <[email protected]> wrote:
> 
> > Suggestion - make 3.5 a very short release, consisting mainly of getting
> > as many fixes in as we can, and giving them a proper testing. It's an
> > opportunity for us Guides to warm up at doing the whole process
> > ourselves. I'm talking about a time scale of 1 month total - 2 weeks
> > alpha, 1 week beta, 1 week gamma, release.
> I find it just about impossible to imagine getting stuff done that
> quickly given the geographic and chronologic spread of people involved.
> It'll take more than two weeks before any decent number of people heve
> even downloaded 3.4, let alone done anything much to find and fix any
> bugs.
> 
> For topics to cover
>  + relating to the vm, how about incorporating any removal of vm/slang
>  code that we can manage - JMM & I have been trying to get a decent
>  release of codegen stuff together and can probably produce a removal
>  update and re-install package.
>  + in the image, how about the remove-b3d etc changes?
>  + how about declaring that only fixes released by a certain date will
>  be considered and that after that only comment improvements will be
>  accepted ?
> 
> tim
> 
> -- 
> Tim Rowledge, [email protected], http://sumeru.stanford.edu/tim
> <-------- The information went data way -------->
> 
> _______________________________________________
> Squeakfoundation mailing list
> [email protected]
> http://lists.squeakfoundation.org/listinfo/squeakfoundation
From [email protected] Mon Mar 03 00:31:10 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 19627 invoked from network); 3 Mar 2003 00:31:10 -0000
Received: from mxout3.netvision.net.il (194.90.9.24)
  by mail.theinternetone.net with SMTP; 3 Mar 2003 00:31:10 -0000
Received: from [80.178.112.97] ([80.178.112.97]) by mxout3.netvision.net.il
 (iPlanet Messaging Server 5.2 HotFix 1.08 (built Dec  6 2002))
 with SMTPA id <[email protected]> for
 [email protected]; Mon,
 03 Mar 2003 02:31:10 +0200 (IST)
Date: Mon, 03 Mar 2003 02:18:47 +0300
From: Daniel Vainsencher <[email protected]>
Subject: Re: [Squeakfoundation]Re: Collecting tests?
To: Discussing the Squeak Foundation
 <[email protected]>
Message-id: <[email protected]>
X-Mailer: Celeste 2.0.5108
Content-transfer-encoding: 7BIT
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: Mon, 03 Mar 2003 00:31:12 -0000

And how do you build that image? using a loading script. If you have
loading scripts, why not have them in SM, to be shared by all?

Dependencies are not that far off...

Daniel

Marcus Denker <[email protected]> wrote:
> (For the 3.5 release we could tink about a scheme where we have a
> "base image" (as much removed as possible) and a "release image"
> (An image with most of the functionality as today, but build from
> installing packages into the base image). 
> 
> With such a scheme we could start taking Squeak apart even without
> having to wait for SqueakMap supporting dependencies and virtual
> packages (aka Distributions).
> 
> 
>      Marcus
> 
> -- 
> Marcus Denker [email protected]  -- Squeak! http://squeak.de
> 
> _______________________________________________
> Squeakfoundation mailing list
> [email protected]
> http://lists.squeakfoundation.org/listinfo/squeakfoundation
From [email protected] Mon Mar 03 00:31:11 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 19707 invoked from network); 3 Mar 2003 00:31:11 -0000
Received: from mxout3.netvision.net.il (194.90.9.24)
  by mail.theinternetone.net with SMTP; 3 Mar 2003 00:31:11 -0000
Received: from [80.178.112.97] ([80.178.112.97]) by mxout3.netvision.net.il
 (iPlanet Messaging Server 5.2 HotFix 1.08 (built Dec  6 2002))
 with SMTPA id <[email protected]> for
 [email protected]; Mon,
 03 Mar 2003 02:31:11 +0200 (IST)
Date: Mon, 03 Mar 2003 02:27:39 +0300
From: Daniel Vainsencher <[email protected]>
Subject: [Squeakfoundation]Re: Outstanding 3.4 bugs?
To: Discussing the Squeak Foundation
 <[email protected]>
Message-id: <[email protected]>
X-Mailer: Celeste 2.0.5108
Content-transfer-encoding: 7BIT
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: Mon, 03 Mar 2003 00:31:13 -0000

Simon, the reason I very much am waiting to hear Doug on this topic, and
speaking about 1 month releases should be very tentative, is that none
of us has Actually Done It. Doug might know how much the price of a
release is, and how much it might be reduced, and whether he has time
for it/someone else can do it in reasonable time, and those'll be the
prime considerations in deterimining how often it will happen.

Even doing only a short first release (without setting a fixed rythm
yet), as I propose, depends on these parameters.

Daniel

Simon Michael <[email protected]> wrote:
> Tim Rowledge <[email protected]> writes:
> > I find it just about impossible to imagine getting stuff done that
> > quickly given the geographic and chronologic spread of people involved.
> > It'll take more than two weeks before any decent number of people heve
> > even downloaded 3.4, let alone done anything much to find and fix any
> > bugs.
> 
> I think it's hard to imagine because we're all used to a different
> process. However, with a steady monthly rhythm and known dates we would
> all soon adjust.  Eg when the world knows that "3.x comes out on the 1st"
> it will get downloaded a lot quicker. If bugs or major enhancements aren't
> ready in time for the release, fine, they show up next month (or the month
> after or..). 
> 
> NB in the worst case, release time rolls around and noone's had time to do
> anything this month, we'd be just re-releasing (we'd probably skip that
> one). That's fine. The larger process is far more important.
> 
> Of course we can debate the optimal duration of an "iteration" - one
> month, two months, three.. personally I feel one month works here. A
> faster cycle allows us to learn and improve the process more quickly.
> _______________________________________________
> Squeakfoundation mailing list
> [email protected]
> http://lists.squeakfoundation.org/listinfo/squeakfoundation
From [email protected] Mon Mar 03 04:49:56 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 6316 invoked from network); 3 Mar 2003 04:49:56 -0000
Received: from mailhost1-sfldmi.sfldmi.ameritech.net (HELO
	mailhost.det2.ameritech.net) (206.141.193.105)
	by mail.theinternetone.net with SMTP; 3 Mar 2003 04:49:56 -0000
Received: from riskmetrics.com ([66.72.186.201])
	by mailhost.det2.ameritech.net
	(InterMail vM.4.01.02.17 201-229-119) with ESMTP
	<20030303044954.JEVY8853.mailhost.det2.ameritech.net@riskmetrics.com>;
	Sun, 2 Mar 2003 23:49:54 -0500
Date: Sun, 2 Mar 2003 23:49:54 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
To: [email protected]
From: Doug Way <[email protected]>
Content-Transfer-Encoding: 7bit
Message-Id: <[email protected]>
X-Mailer: Apple Mail (2.551)
cc: Discussing the Squeak Foundation
	<[email protected]>
Subject: [Squeakfoundation][UPDATES] 3.4 is now final
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: Mon, 03 Mar 2003 04:49:57 -0000


Hello all, 3.4 is now finalized!

I just issued an update offering the choice of moving a 3.4gamma image 
to 3.4, or to 3.5alpha.  (Technically, the choice was already offered 
in an earlier update when 3.4gamma was created, but since the two 
update streams contain the same fixes, I offered the choice again.)

A 3.4 final image/changes/readme .zip file is available on the ftp 
site, here:

ftp://st.cs.uiuc.edu/Smalltalk/Squeak/3.4/

Please give this a quick test if you have a chance, just to make sure 
there are no major problems with the image.  A major problem roughly 
meaning: any significant problem which was *not* in 3.4gammaOne.

This image should be identical to 3.4gammaOne, except for incorporating 
the last update (5170), and some content changes in the Welcome... 
window, which were discussed on the SqF list (on Feb. 4 & 8).

The 3.4 release is still not complete in the sense that the squeak.org 
downloads page has not been updated to point to the appropriate 3.4 
bundles.  When that is done, that will be the true "release date" for 
3.4.  Allowing a few days to make sure there are no major problems with 
this image, and also to create the release bundles with VMs, I think we 
should shoot for updating squeak.org in 3-4 days.

Anyway, I'd like to thank Scott Wallace for spending time helping me 
get the update stream going, and with all of the release details.  And, 
of course, thanks to all of SqC for "releasing" Squeak to the Guides 
and the community at large!

- Doug Way