[Moose-dev] Re: Release process for Moose components and subcomponents

Stef, Just to be sure I understand our goal properly: We want to create a stable version with versioner at the end of the week. A stable version is a version that only gets approved changes (where we can have discussion about when a change gets approved for moose …). If we want a snapshot (no bug fixes allowed, 100% reproducible), we should not pollute the configuration with it. And then we need to have a complete list with all packages. That means: that we need a snapshot of Pharo too. I am currently taking a look at versioner and trying to determine if this workflow would be acceptable. I tried it on Moose and and Glamour. And this is the problems I have: - The comment on the release button says: create a new version and a new baseline. Pressing the button does not create a new baseline (this is good), so please fix the comment here. - Pressing the button suggests it resolves all symbolic dependencies to actual versions. I want more control here. In Moose the correct version for Grease is currently #’release1.1’. For Magritte3 this should be #’release3.1’. - Dialog is way too small: I cannot see the version number I am creating. - The suggested version number is incorrect. I.e. for moose it should be 5.0 or 5.0.0. For glamour it should be 2.9 or 2.9.0. - Looking at the version: - both common blocks define author, timestamp, blessing and description. These problems should be fixed before we can do this. And of course, we should check for all projects if the result is the desired result. Diego On 30 Jun 2014, at 10:32, stepharo <stepharo(a)free.fr> wrote: