[Io] Picking up where we left it

[Ken Causey]

OK, so do I understand correctly that what we are then at least
attempting to do is all cooperate in growing a single 'version' of the
image (a specific public version + the team's shared monticello update)?
This is in contrast to use each producing a 'diff' from the published
image, and someone else (possibly the team leader) merging these into a
single monticello package which is then sent to the release team.

If I'm understanding this correctly, what happens then when a new public
3.9x version is released?  At that point we need to know whether or not
what we had been producing has been submitted to the release team and
incorporated into the released 3.9x version.

You may feel I'm picking at nits here.  But I know we had problems with
this when we started the Network team.  I'm not saying we can come up
with an absolute answer right now.  But I am saying this needs to be
given some thought and maybe when we get started we need to be in fairly
close communication and someone needs to be monitoring the resulting
product to see if it's going to work.

Ken

On Wed, 2006-03-15 at 23:12 +0100, Cees De Groot wrote:
> Resuming my proposal:
> 
> - you take the latest image from the 3.9a pub ftp dir;
> - you load in there the latest MC version from the Team's repository.
> - hack away;
> - save to the Team's repository;
> - check for newer versions since you updated, if yes:
> - - merge;
> - - save new version.
> - lather, rinse, repeat.
> 
> Something like that?
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/io/attachments/20060315/9d797ecb/attachment.pgp