Before I get into details, if you create a new Configuration in Pharo, you will get now a pre-filled template with lots of comments.
Summary: ======== - only 1 version for development which is updated manually (typically on each new commit) - for the DEV version, there is a DEV baseline - if a new release happens, the dev version and it's baseline are copied, the baseline has the same version number as the first version it was introduced with. - all external projects in separate methods for readability (plus it's easier to change the main repos) It's not much actually, but basically I treat the configuration as normal ST code and avoid duplication :). I hope my explanation is not clear enough. On 2013-08-10, at 04:35, Stéphane Ducasse <[email protected]> wrote: > Hi camillo > > I like the pattern damien told me you are applying for your configuration. > Could you explain them? > I understood: > > baseline48: spec > <version: '4.8-baseline'> > > spec repository: 'http://www.smalltalkhub.com/mc/Moose/Moose/main'. > … > spec project: 'Metanool' with: [ > spec > className: 'ConfigurationOfMetanool'; > version: #development; > file: 'ConfigurationOfMetanool'; > repository: > 'http://www.smalltalkhub.com/mc/Moose/Metanool/main' ]. > > … > > => > > baseline48: spec > <version: '4.8-baseline'> > > spec repository: self repositoryUrlString > … > spec project: 'Metanool' with: [ > spec > className: 'ConfigurationOfMetanool'; > version: #development; > file: 'ConfigurationOfMetanool'; > repository: > 'http://www.smalltalkhub.com/mc/Moose/Metanool/main' ]. > > … > > repositoryUrlString > ^ 'http://www.smalltalkhub.com/mc/Moose/Moose/main'. > > specMetanoolConfiguration: spec > > spec > className: 'ConfigurationOfMetanool'; > version: #development; > file: 'ConfigurationOfMetanool'; > repository: > 'http://www.smalltalkhub.com/mc/Moose/Metanool/main' > > > > > I like the idea to avoid duplication at the configuration level. > Now damien mention a dev and stable baseline > > Stef > > >
