Yes, I understand for the developer version, you should have a developer branch and use that. The problem is for the Pharo image only.
On Mon, Mar 5, 2018 at 3:39 PM, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: > Hi, > > it is an issue of Calypso dependencies. I discussed it with Denis > before Calypso integration and he would like to change it but, for > now, it would make the development for him much harder because he > needs a way how to load the latest bleeding edge versions of the > packages and no one was able to tell him the proper way how to support > both scenarios (loading of a specific release and loading of the > development versions) with baselines without needing of duplicate > them. > > Anyway, I agree that the current state must be fixed as soon as possible. > > Cheers, > -- Pavel > > 2018-03-05 15:30 GMT+01:00 teso...@gmail.com <teso...@gmail.com>: > > Hello, > > i have seen in the latest version of Pharo baselines pointing to > > "floating" versions. A version that is not fixed. I want to know why > this is > > like that? > > > > To me this is basically wrong, because basically this goes against the > idea > > of having repeatable builds. Also using semantic versions with tags in > Git > > is wrong, as tags should be immutable (that is why you have to use > --force > > to update them, in Guille's words "If you have to force it, it is not > > good"). > > > > Cheers, > > > > -- > > Pablo Tesone. > > teso...@gmail.com > > -- Pablo Tesone. teso...@gmail.com
