[squeak-dev] Squeak release process

Frank Shearar frank.shearar at gmail.com
Mon Jul 16 11:40:34 UTC 2012

On 16 July 2012 12:27, Edgar J. De Cleene <edgardec2005 at gmail.com> wrote:
> On 7/16/12 8:10 AM, "Frank Shearar" <frank.shearar at gmail.com> wrote:
>> Hi Edgar,
>> I saw several such pages. Those tell me what went into 3.10, 4.3, etc.
>> I'm not talking about those. I'm talking about a checklist that anyone
>> can follow to produce/manage a new Squeak release. For example
>> * Warn of a code freeze no later than 4 weeks before the due release date
>> Pre-release planning and announcements
>> * Ensure that all tests pass. Any failing tests that cannot be fixed
>> marked as expected failures
>> * and
>> * so
>> * on
>> Release time
>> * Add a new category to Mantis for the release
>> * Prepare release notes, published to squeak-dev for comment. In the
>> absence of comments, assume that the notes are fine.
>> * Publish the artifacts to ___.
>> Post-release cleanup
>> * Unmark the expected failures marked earlier, so someone can actually fix
>> them
>> Also, of course we have a release team. We just don't have a
>> _dedicated_ release team. And we shouldn't, for good reason: a
>> dedicated release team is an excuse for everyone else to assume that
>> the release team bears full responsibility for the process.
>> frank
> All you said was the process followed...

I think we're not talking about the same thing. I would like to see a
checklist that a release team can follow. I don't know where I can
find such a checklist. There might be one buried on the Swiki, but I
couldn't find it.


> And a dedicated release team is not excuse for people wishing a better
> Squeak.
> Edgar

More information about the Squeak-dev mailing list