[Release] 3.11 planning

[Ken G. Brown]

At 10:56 PM +0100 5/30/08, Keith Hodges apparently wrote:
>Dear All,
>
>having discovered that we lack concensus... here goes with my idea.
>
>I venture to suggest that every release team performs certain functions...
>
>1. Harvesting Fixes
>2. Removing Deprecated Stuff
>3. Loading the latest and greatest packages
>4. Producing some documentation for workspaces etc.
>
>My plan is to take each potential activity as a sub-project, whose results generate either a script on installer.pbwiki.com or a Sake/Task.
>
>So to generate a release candidate for testing we run the script end to end assembling all of the parts for example.
>
>3.10 + MinorFixes + PackageUpgrades + Clean.
>
>
>This produces a cantidate for 3.11, well at least the proposed content for 3.11, we then look at how to deliver it using the new tools we are developing.
>
>Option 1. Run the script using using DS to record all of the changes made to the image, then generate a cs from that which can be placed upon the update stream.
>
>Option 2. Save all packages from the prototype image to MC.
>
>Generate 3.11 by taking 3.10 and loading in all the latest packages from MC. (requires atomic loading)
>
>Having done this...
>
>3.12 becomes 3.11 + MinorFixes + PackageUpgrades + Clean
>
>and we go around again every 6 months or so.
>
>Keith
>

I think it might be a good idea to plan for a way to save a snapshot of the base starting image as well as all the scripts that were run to create the version. I'm thinking It would be good to always be able to recreate a version from whatever starting point was captured.

Ken G. Brown

>_______________________________________________
>Release mailing list
>Release at lists.squeakfoundation.org
>http://lists.squeakfoundation.org/mailman/listinfo/release