On Sat, Jul 7, 2012 at 11:16 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

PharoVM configuration names are following this rule:

pharoversion-buildversion

so, 2.0-1 is the first build made for pharo 2.0...

something like that. Yeah, I don't like the numbering, but I also don't like the M.m (Major.minor) standard, because we don't know what is major and what minor... so, right now is just 1.9 then 2.0 without actually having a major change.. and it is confusing, because it looks like important, but actually it does not means anything at all :)

Esteban

On Jul 7, 2012, at 9:03 PM, Sean P. DeNigris wrote:

> I noticed the versions vary between x.x.x and x.x-x and that some of the
> versions import baselines and others import other versions. I've never seen
> it done like that... what's the intention?
>
> e.g.
> "Baseline with dot imported by version with dash"
> version145: spec
> � � � <version: '1.4-5' imports: #('1.4.1-baseline')>
>
> "version importing another version"
> version143: spec
> � � � <version: '1.4-3' imports: #('1.4-2')>
>
> Cheers,
> Sean
>
> --
> View this message in context: http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>