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 <[email protected]> wrote: > 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <[email protected]>: > >> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <[email protected]> >> 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
