Diego, I realize that you may not like the name #stable, but the mechanism behind #stable is what you want. In current usage, the #stable version is the 'recommended version'..... Dale ----- Original Message ----- | From: "Diego Lont" <diego.lont@delware.nl> | To: pharo-project@lists.gforge.inria.fr | Sent: Monday, April 22, 2013 5:39:19 AM | Subject: Re: [Pharo-project] (was: Moose-dev) #stable and Metacello | | Dale, Stef, | | I like to have "a recommended version" as default and not #'stable'. Because | I still want to recommend a version, even is this isn't stable. I can use | the blessings to mark it as "development" or "release". | | Using a 'recommended version' also makes it clear, that it depends on the | project (both using as used) wether is is wise to use this version or not. | For Moose 4.8 the 'recommended version' is the release candidate. | | Diego | | On Apr 18, 2013, at 9:55 PM, stephane ducasse wrote: | | > | > On Apr 18, 2013, at 6:29 PM, Dale Henrichs <dhenrich@vmware.com> wrote: | > | >> Stef, | >> | >> I think it is clear that #stable is not the right name, but I also think | >> it is better to have one "badly named," commonly used symbolic version | >> rather than a bunch of different names for the same thing⦠| > | > yes | > but this can be confusing. | >> Eventually we should change the convention, but I don't think we need to | >> hurry and do so:) | > | > first we need a tool to manage configuration for real. | > | > Stef | > | >> | >> Dale | >> | >> ----- Original Message ----- | >> | From: "stephane ducasse" <stephane.ducasse@free.fr> | >> | To: "Moose-related development" <moose-dev@iam.unibe.ch> | >> | Sent: Wednesday, April 17, 2013 10:04:50 PM | >> | Subject: [Moose-dev] Re: #stable and Metacello (was Re: | >> | ConfigurationOfGlamourSeaside) | >> | | >> | Dale | >> | | >> | I thought that stable should be called milestoneDevelopment. | >> | I will add a note to the metacello chapter and versionner will handle | >> | the | >> | patterns we see. | >> | | >> | Stef | >> | |