Thanks dale I should have tried. I will discuss with the CI guru here and probably the > spec for: #'common' version: '1.1-baseline'
which is what I'm looking for. I will add that to the book :) > > For the #development symbolic version you can use any version that you'd like > (including another symbolic version) so you could do any one of the following: > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: '1.1' > > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: '1.1-baseline' > > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: #stable > > Does that help? > > Dale > > > ----- Original Message ----- > | From: "Stéphane Ducasse" <[email protected]> > | To: "[email protected] Development" > <[email protected]> > | Cc: "Dale Henrichs" <[email protected]> > | Sent: Sunday, March 3, 2013 1:51:18 AM > | Subject: About development on symbolic versions > | > | Hi dale > | > | for pharo 3.0 alpha I want the following setup. > | > | I want to monitor all the pharo-contribution using jenkins. So is there a > | pattern to make sure that at the same > | time I can load the stable version of the project on 2.0 but the development > | baseline for the 3.0 (which may match the 20 if no change are made)? > | > | for example for XMLParser I have > | > | stable: spec > | <symbolicVersion: #'stable'> > | > | spec for: #'common' version: '1.1'. > | > | > | now what should I write for development? > | > | development: spec > | <symbolicVersion: #'development'> > | > | spec for: #'common' version: ???? > | > | Thanks
