Re: 3.6 MasterPlanner!?

Howdy all!

(Ahhh, how nice to not discuss licensing issues :-) )

Doug Way <[email protected]> wrote: 
> > [email protected] wrote:
> > > 
> > > ...
> > > Ok, so lets be quick here - Ned, Tim or Me+Doug? And please don't start
> > > discussing the need for someone doing this - Doug wants someone and he
> > > *is* in charge of the update stream so darnit, just accept the fact that
> > > we need someone doing this. :-)
> 
> Ok, since neither Ned, Tim nor Craig volunteered for this task, I think we
> should go with the Goran+Doug master planner plan, so we can move forward.  I
> can understand that no one might jump at volunteering for this particular
> task... it could make one rather unpopular.  But if it's going to be
> Goran+Doug, I can simply blame Goran for any poor decisions. ;-)

Right! I seem to have some nice Karma right now that I can burn on bad
decisions. :-)

You and me it is then... Muuuaahahahaha! (loud evil laughter as the
thought sinks in)

> > > As soon as we have this decided the MasterPlanner(s) should probably IMO
> > > start a quick "round up" thread on squeak-dev to collect ideas on what
> > > 3.6 will/should/could be made of.
> 
> Um, yes.  You can start that up if you'd like.

I will do that. I will start by scanning all the relevant posts that
already have been made on the subject and build a "gross shopping list"
which we can pick and choose from. I will also post on squeak-dev that
we are currently doing this to encourage postings on the subject.
 
> One thing about the plan that I think we have agreed on to some extent is the
> 4-month time period, and the notion that the release date would generally be
> more firm than the release content.  When I proposed this, there was some
> agreement, and no disagreement.  With the First Fridays system, the release
> date would be August 1st.  So, if there are no last-minute disagreements,
> let's consider this part of the plan as set in stone.

Exactly.

> Other than that, I think Daniel's list of items below is a good start.  Some
> items such as the "simulator fixes by Craig" might even be a finer level of
> granularity than is necessary for a release plan.  Most bug fixes do not
> really need to be in the plan.  However, if the simulator fixes are
> large/significant fixes, then sure, we can include them in the plan.

I agree - we don't need to include simple small FIXes, that is
definitely not the point of the plan.
But I do want us to decide on the bigger issues. And then, as you wrote
- the release date will always limit what actually get in, in the end.

> Items I might add to the list are:
> 
> * Apply some number of package removals to the image.  (Perhaps you were
> taking this one for granted.)  I don't think we should try to plan exactly
> which ones will be removed, but we could set a rough goal of a certain number
> of MB removed from the image, perhaps.
> * Remove the Apple fonts from the image, and replace them with functionally
> similar bitmap fonts.  We would still need to decide whether this meant the
> Accufonts, or a move to ISO-8859-1.

Will collect.

Oh, and yeah:

> Daniel Vainsencher wrote:
> > 
> > Ok, Goran, I can see when I'm beaten :-)
> > 
> > Since I'm still not interested in taking this as a fixed role, and
> > you've decided it's needed, I don't mind if you and Doug (or someone
> > else) take it up. Heck, I'll even help along occaisonally. While I'm at

Actually I wasn't proposing this as a "fixed role" (sorry if it sounded
like that) - I was merely proposing the role for 3.6. After that someone
else may take the wheel! :-)

regards, Göran
From [email protected] Sat Apr 05 15:48:28 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 18004 invoked from network); 5 Apr 2003 15:48:28 -0000
Received: from mailout.whidbey.net (209.166.64.124)
  by mail.theinternetone.net with SMTP; 5 Apr 2003 15:48:28 -0000
Received: from vdsl-72-234.whidbey.net ([209.166.72.234] helo=ned)
	by mail4.whidbey.net with esmtp (Exim 4.12)	id 191pta-0001Gv-00
	for [email protected];
	Sat, 05 Apr 2003 07:47:54 -0800
From: Ned Konz <[email protected]>
To: Discussing the Squeak Foundation
	<[email protected]>
Subject: Re: [Squeakfoundation]How to proceed for the kernel cleaning
	harvesting
Date: Sat, 5 Apr 2003 07:47:47 -0800
User-Agent: KMail/1.5.1
References: <[email protected]>
In-Reply-To: <[email protected]>
X-Image-URL: http://bike-nomad.com/nedicon.jpg 
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[email protected]>
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: Sat, 05 Apr 2003 15:48:29 -0000

On Friday 04 April 2003 11:25 pm, Stephane Ducasse wrote:
> Now the problem is that cleaning the kernel is somehow special and
> the order of the changesets may be really important. So change 0001
> should be put in before 0004 for example. We are focusing on
> specific parts and we have some major milestones as explained on
> the page. http://minnow.cc.gatech.edu/squeak/3083
[snip]
> So as soon as our own reviewing process will finish for the first
> 40 changesets we will send them into the stream. But we would like
> to know how to minimize energy.

Hi Stef,

What I would do (given that the order is important) is to package them 
(and their test suites) all into a .SAR whose install/preamble loads 
them in the right order.

They can still be reviewed independently (as they'll retain their 
identity in the ChangeSorter).

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE