March 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Pavel Krivanek

as far as I understand it, you have this: Calypso v1 - Commander v1 - ClassAnnotations v1 You are working on and you fix a version in ClassAnnotations Calypso v1 - Commander v1 - ClassAnnotations v2 but you still do not want to make it as a release. When rebuilding your image, you want to be able to load all three packages in the latest state. Then you make a new change in Calypso Calypso v2 - Commander v1 - ClassAnnotations v2 and you want to mark this dependency tree as a new release version -- Pavel 2018-03-05 16:57 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > But can you explain me the scenario? I still don't understand it :( > > On Mon, Mar 5, 2018 at 4:51 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Maybe we should just load Calypso dependencies explicitly. >> In any case they will be used by other projects. Like new Iceberg will >> use Commander. And ClassAnnotation will be in Kernel. >> So we will need to load them in another time than Calypso. >> >> Now we can just put them directly into #loadCalypso method. (there are >> three dependencies) >> It will fix my problem and make Pharo build reproducible. >> >> 2018-03-05 16:38 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: >> >>> But, "one single class" does not mean anything. Because it depends from >>> which branch/commitish you are loading it from... >>> >>> Can you explain better what is the problem because I am not getting it... >>> >>> In any case, independently of where is the burden, I want to veto any >>> new integration that may make future builds non-reproducible. Otherwise >>> this is a source of chaos and dead kittens. >>> >>> On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>>> 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: >>>> >>>>> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>>>> wrote: >>>>> > Hi Pablo. >>>>> > >>>>> > Dev branch approach not really works. Because any merge into master >>>>> will >>>>> > break master baseline. (notice that baseline is in same repo). >>>>> > And managing merges by hand all the time is not a solution. >>>>> > >>>>> > >>>>> Hi! >>>>> If you don't want to manage the merges by hand you can maybe have two >>>>> bsaelines? >>>>> BaselineOfCalypso and BaselineOfCalypsoDev? >>>>> >>>> >>>> It should work. But is it right way that everybody should follow? >>>> >>>> With configurations it was easy to do in single class. >>>> >>>> >>>>> >>>>> -- >>>>> Cyril Ferlicot >>>>> https://ferlicot.fr >>>>> >>>>> >>>> >>> >>> >>> -- >>> >>> >>> >>> Guille Polito >>> >>> Research Engineer >>> >>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>> >>> CRIStAL - UMR 9189 >>> >>> French National Center for Scientific Research - *http://www.cnrs.fr >>> <http://www.cnrs.fr>* >>> >>> >>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>> >>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>> >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Cyril Ferlicot

On Mon, Mar 5, 2018 at 4:51 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > I still do not understand... Also I do not understand your usage of the > term "the merge". Can somebody give a **concrete** scenario? > > I'll try For example the project MaterialDesignLite have two branches that are always here: - master - development Each commit on master is a stable release and end up with a tag as "v1.2.2". Since it's stable, BaselineOfMaterialDesignLite should depend only on fixed version of the dependencies. For example it should depend on MaterialDesignColor "v1.0.0". On the branch dev, we want to get the patches and possibly the minor versions of the dependencies automatically. In the baseline we then want to depend on MaterialDesignColor "v1.x.x". Thus, we follow the changes of MaterialDesignColor while it's not a major release. Because of this situation, BaselineOfMaterialDesignLite is different on the two branches. Later, if I want to merge development into master in order to release a new version, master will get the BaselineOfMaterialDesignLite with semantic versionning dependencies instead of the fixed dependencies. Before the release I'll need to change the Baseline to get fix dependencies once again. I hope I was clearer. :) > When you release a version, please do not move that version. You should > then create new versions, with new numbers and new code. But never touch > old versions with old numbers and old code. Like that I can download the > same old code using the same old number to get the old version whenever I > want :). > > You can try to do it with branches, tags, different repositories, or even > with zipfiles in mails. I don't care. Just don't modify releases and I'm > happy with it. > > > > -- Cyril Ferlicot https://ferlicot.fr

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Guillermo Polito

But can you explain me the scenario? I still don't understand it :( On Mon, Mar 5, 2018 at 4:51 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Maybe we should just load Calypso dependencies explicitly. > In any case they will be used by other projects. Like new Iceberg will use > Commander. And ClassAnnotation will be in Kernel. > So we will need to load them in another time than Calypso. > > Now we can just put them directly into #loadCalypso method. (there are > three dependencies) > It will fix my problem and make Pharo build reproducible. > > 2018-03-05 16:38 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> But, "one single class" does not mean anything. Because it depends from >> which branch/commitish you are loading it from... >> >> Can you explain better what is the problem because I am not getting it... >> >> In any case, independently of where is the burden, I want to veto any new >> integration that may make future builds non-reproducible. Otherwise this is >> a source of chaos and dead kittens. >> >> On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: >>> >>>> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>>> wrote: >>>> > Hi Pablo. >>>> > >>>> > Dev branch approach not really works. Because any merge into master >>>> will >>>> > break master baseline. (notice that baseline is in same repo). >>>> > And managing merges by hand all the time is not a solution. >>>> > >>>> > >>>> Hi! >>>> If you don't want to manage the merges by hand you can maybe have two >>>> bsaelines? >>>> BaselineOfCalypso and BaselineOfCalypsoDev? >>>> >>> >>> It should work. But is it right way that everybody should follow? >>> >>> With configurations it was easy to do in single class. >>> >>> >>>> >>>> -- >>>> Cyril Ferlicot >>>> https://ferlicot.fr >>>> >>>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

Maybe we should just load Calypso dependencies explicitly. In any case they will be used by other projects. Like new Iceberg will use Commander. And ClassAnnotation will be in Kernel. So we will need to load them in another time than Calypso. Now we can just put them directly into #loadCalypso method. (there are three dependencies) It will fix my problem and make Pharo build reproducible. 2018-03-05 16:38 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > But, "one single class" does not mean anything. Because it depends from > which branch/commitish you are loading it from... > > Can you explain better what is the problem because I am not getting it... > > In any case, independently of where is the burden, I want to veto any new > integration that may make future builds non-reproducible. Otherwise this is > a source of chaos and dead kittens. > > On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: >> >>> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> > Hi Pablo. >>> > >>> > Dev branch approach not really works. Because any merge into master >>> will >>> > break master baseline. (notice that baseline is in same repo). >>> > And managing merges by hand all the time is not a solution. >>> > >>> > >>> Hi! >>> If you don't want to manage the merges by hand you can maybe have two >>> bsaelines? >>> BaselineOfCalypso and BaselineOfCalypsoDev? >>> >> >> It should work. But is it right way that everybody should follow? >> >> With configurations it was easy to do in single class. >> >> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Guillermo Polito

On Mon, Mar 5, 2018 at 4:45 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Mon, Mar 5, 2018 at 4:38 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> But, "one single class" does not mean anything. Because it depends from >> which branch/commitish you are loading it from... >> >> Can you explain better what is the problem because I am not getting it... >> >> In any case, independently of where is the burden, I want to veto any new >> integration that may make future builds non-reproducible. Otherwise this is >> a source of chaos and dead kittens. >> >> The problem is that actually if you have a git project with a stable and > dev branch you will need: > - One baseline on the stable branch with determined dependencies versions > - One baseline on the dev branch with less restricted versions (for > example 3.x.x) > Then, when you release a new stable version by merging the development > branch you need to edit the merge by hand to merge everything except the > baseline. > I think this is what Denis wants to avoid. > But in general, such merges need to be done only for major and minor > releases. Not for a patch because you can do a hotfix. You create a new > branch from master, then merge in in master and development when it's done. > I still do not understand... Also I do not understand your usage of the term "the merge". Can somebody give a **concrete** scenario? When you release a version, please do not move that version. You should then create new versions, with new numbers and new code. But never touch old versions with old numbers and old code. Like that I can download the same old code using the same old number to get the old version whenever I want :). You can try to do it with branches, tags, different repositories, or even with zipfiles in mails. I don't care. Just don't modify releases and I'm happy with it. > > -- > Cyril Ferlicot > https://ferlicot.fr > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Cyril Ferlicot

On Mon, Mar 5, 2018 at 4:38 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > But, "one single class" does not mean anything. Because it depends from > which branch/commitish you are loading it from... > > Can you explain better what is the problem because I am not getting it... > > In any case, independently of where is the burden, I want to veto any new > integration that may make future builds non-reproducible. Otherwise this is > a source of chaos and dead kittens. > > The problem is that actually if you have a git project with a stable and dev branch you will need: - One baseline on the stable branch with determined dependencies versions - One baseline on the dev branch with less restricted versions (for example 3.x.x) Then, when you release a new stable version by merging the development branch you need to edit the merge by hand to merge everything except the baseline. I think this is what Denis wants to avoid. But in general, such merges need to be done only for major and minor releases. Not for a patch because you can do a hotfix. You create a new branch from master, then merge in in master and development when it's done. -- Cyril Ferlicot https://ferlicot.fr

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

In Configuration I defined two baselines: dev and stable. In dev baseline I referenced dev version of dependencies. In stable I referenced stable version of dependencies. 2018-03-05 16:38 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > But, "one single class" does not mean anything. Because it depends from > which branch/commitish you are loading it from... > > Can you explain better what is the problem because I am not getting it... > > In any case, independently of where is the burden, I want to veto any new > integration that may make future builds non-reproducible. Otherwise this is > a source of chaos and dead kittens. > > On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: >> >>> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> > Hi Pablo. >>> > >>> > Dev branch approach not really works. Because any merge into master >>> will >>> > break master baseline. (notice that baseline is in same repo). >>> > And managing merges by hand all the time is not a solution. >>> > >>> > >>> Hi! >>> If you don't want to manage the merges by hand you can maybe have two >>> bsaelines? >>> BaselineOfCalypso and BaselineOfCalypsoDev? >>> >> >> It should work. But is it right way that everybody should follow? >> >> With configurations it was easy to do in single class. >> >> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Guillermo Polito

But, "one single class" does not mean anything. Because it depends from which branch/commitish you are loading it from... Can you explain better what is the problem because I am not getting it... In any case, independently of where is the burden, I want to veto any new integration that may make future builds non-reproducible. Otherwise this is a source of chaos and dead kittens. On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > >> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> > Hi Pablo. >> > >> > Dev branch approach not really works. Because any merge into master will >> > break master baseline. (notice that baseline is in same repo). >> > And managing merges by hand all the time is not a solution. >> > >> > >> Hi! >> If you don't want to manage the merges by hand you can maybe have two >> bsaelines? >> BaselineOfCalypso and BaselineOfCalypsoDev? >> > > It should work. But is it right way that everybody should follow? > > With configurations it was easy to do in single class. > > >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Hi Pablo. > > > > Dev branch approach not really works. Because any merge into master will > > break master baseline. (notice that baseline is in same repo). > > And managing merges by hand all the time is not a solution. > > > > > Hi! > If you don't want to manage the merges by hand you can maybe have two > bsaelines? > BaselineOfCalypso and BaselineOfCalypsoDev? > It should work. But is it right way that everybody should follow? With configurations it was easy to do in single class. > > -- > Cyril Ferlicot > https://ferlicot.fr > >

March 5, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Denis Kudriashov

Also it is not really development versions. I follow semantics versioning. So I reference 0.3.x versions to get all minor fixes from dependencies. 2018-03-05 15:57 GMT+01:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > 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.krivanek(a)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 tesonep(a)gmail.com <tesonep(a)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. >> > tesonep(a)gmail.com >> >> > > > -- > Pablo Tesone. > tesonep(a)gmail.com >

March 5, 2018