Hi
today we brainstormed and I will send a sequence of emails to discuss what we decided and started to do.
One of our goal is to check if we can use versionner to manage all the configurations. It looks possible.
The first things we started to do is - make sure that all the configurations of external libraries are correctly defined. In particular we made sure that a version does not depend on a stable one but on a version specific.
- We think that Moose should not depend on baseline of external tools, because we need real reproduceability.
- We started to produce configurations with versionner that do not depend on stable but on exact versions.
- I will continue to see if we can use Versionner because it would simplify the release.
Stef
Yes, it would be great to have a configuration version for each change. But, for some reason, it is hard to have in moose. I spent quite some days trying to fix this
Alexandre
Le 27-06-2014 à 16:40, stepharo stepharo@free.fr a écrit :
Hi
today we brainstormed and I will send a sequence of emails to discuss what we decided and started to do.
One of our goal is to check if we can use versionner to manage all the configurations. It looks possible.
The first things we started to do is
- make sure that all the configurations of external libraries are correctly defined.
In particular we made sure that a version does not depend on a stable one but on a version specific.
We think that Moose should not depend on baseline of external tools, because we need real reproduceability.
We started to produce configurations with versionner that do not depend on stable but on exact versions.
I will continue to see if we can use Versionner because it would simplify the release.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, it would be great to have a configuration version for each change. But, for some reason, it is hard to have in moose. I spent quite some days trying to fix this
Did you try to do it with versionner? Without a tool this is a hell. Now I think that it will work with versionner. In one click I can release a versionned solution. We tried with some configurations of the moose ecosystems and it look like this is working. So I will continue the experience to see if this is working, snaphotcello is not a good solution (it is what is working) but as mentioned Stefan it flattens and pollutes the configuration.
Now if people shout and I will just fork the configurations. Because this is not acceptable that we cannot reload one version of Moose. We could have a release process as follows
- develop on baseline - release every friday on versions
I do not see why this is not possible.
Stef
Alexandre
Le 27-06-2014 à 16:40, stepharo stepharo@free.fr a écrit :
Hi
today we brainstormed and I will send a sequence of emails to discuss what we decided and started to do.
One of our goal is to check if we can use versionner to manage all the configurations. It looks possible.
The first things we started to do is - make sure that all the configurations of external libraries are correctly defined. In particular we made sure that a version does not depend on a stable one but on a version specific.
- We think that Moose should not depend on baseline of external tools, because we need real reproduceability. - We started to produce configurations with versionner that do not depend on stable but on exact versions. - I will continue to see if we can use Versionner because it would simplify the release.Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable Fame
We will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with
Units MooseAlgoRubric SmallDude MetaNool Maggrite3
Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef
Units is now cleaned and can be managed with versionner.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Artefact was nicely working already well.
The development version points to the stable of Units (this is their choice) and not the development. The stable version points to the version 1.2 of Units. Good work guillaume and olivier.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
For Merlin I promoted latest version as stable since it does not hurt.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
For Rubric I added a version + stable information
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
RoelTyper configuration is nice and nothing to be done.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
SmallDude looks scary. The stable version is tagged as broken! Really cool :) and is just from 2011 :) Now I cleaned it.
I kept the dependencies to spec project: 'Moose Core' with: '5.0-baseline'. for now.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Just a thought, maybe offtopic, but that goes in the modularity path... What about adding also a new ´moose´ tab to the configuration browser showing only moose sub-products?
On Sat, Jun 28, 2014 at 11:55 AM, stepharo stepharo@free.fr wrote:
SmallDude looks scary. The stable version is tagged as broken! Really cool :) and is just from 2011 :) Now I cleaned it.
I kept the dependencies to spec project: 'Moose Core' with: '5.0-baseline'. for now.
Stef
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 28/6/14 12:01, Guillermo Polito wrote:
Just a thought, maybe offtopic, but that goes in the modularity path... What about adding also a new ´moose´ tab to the configuration browser showing only moose sub-products?
I think that if I would have got an engineer to work on the catalog distribution this process and infrasturcture could used by any large projects and Moose could have use that. And indeed I have the same idea than you.
Stef
On Sat, Jun 28, 2014 at 11:55 AM, stepharo <stepharo@free.fr mailto:stepharo@free.fr> wrote:
SmallDude looks scary. The stable version is tagged as broken! Really cool :) and is just from 2011 :) Now I cleaned it. I kept the dependencies to spec project: 'Moose Core' with: '5.0-baseline'. for now. Stef On 28/6/14 11:21, stepharo wrote: So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable Fame We will probably ask christophe that versionner on release proposes the choice to use stable or the version. I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3 Now I will probably have to fork some configurations if I cannot publish on the repositories. Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
added a stable and version to deepTraverser
On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Stef, Guillaume and Christophe,
If you fix configurations, you must fix them properly.
I have reviewed 2 configurations now: XMLWriter is no longer valid for Pharo1.x XMLParser is no longer valid for Gemstone and does not have a correct development version. So please revert all changes, because the way you do this now, will only create a lot of upset people.
Regards, Diego
On 28 Jun 2014, at 11:21, stepharo stepharo@free.fr wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable Fame
We will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with
Units MooseAlgoRubric SmallDude MetaNool Maggrite3
Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
How do I know what is correct.
Stef
Stef, Guillaume and Christophe,
If you fix configurations, you must fix them properly.
I have reviewed 2 configurations now: XMLWriter is no longer valid for Pharo1.x XMLParser is no longer valid for Gemstone and does not have a correct development version. So please revert all changes, because the way you do this now, will only create a lot of upset people.
Regards, Diego
On 28 Jun 2014, at 11:21, stepharo stepharo@free.fr wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I will check that after lunch.
Stef, Guillaume and Christophe,
If you fix configurations, you must fix them properly.
I have reviewed 2 configurations now: XMLWriter is no longer valid for Pharo1.x XMLParser is no longer valid for Gemstone and does not have a correct development version. So please revert all changes, because the way you do this now, will only create a lot of upset people.
Regards, Diego
On 28 Jun 2014, at 11:21, stepharo stepharo@free.fr wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
XMLWriter XMLParser Pastell PhExample OrderPreserving BitmapCharacterSet HashTable FameWe will probably ask christophe that versionner on release proposes the choice to use stable or the version.
I will continue with Units MooseAlgoRubric SmallDude MetaNool Maggrite3Now I will probably have to fork some configurations if I cannot publish on the repositories.
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Diego Lont -
Guillermo Polito -
stepharo