Hi alex
Why Roassal depends on FuelMetalevel?
- having the stable as a baseline is not nice because clients will cry big times. - there is no correct version and it would be good to use versionner to manage it and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
- unique version is pure junk and looks like from a tutorial so I can clean it.
- versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Stef
Why Roassal depends on FuelMetalevel?
Because Roassal1 has a feature to export view using Fuel. This was never really used actually.
- having the stable as a baseline is not nice because clients will cry big times.
- there is no correct version and it would be good to use versionner to manage it
and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
unique version is pure junk and looks like from a tutorial so I can clean it.
versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Which version of Roassal are you referring to? Roassal 1 or 2?
Alexandre
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
Doru
On Sun, Jun 29, 2014 at 2:14 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
Why Roassal depends on FuelMetalevel?
Because Roassal1 has a feature to export view using Fuel. This was never really used actually.
- having the stable as a baseline is not nice because clients will cry
big times.
- there is no correct version and it would be good to use versionner to
manage it
and to release some versions from time to time. Now that roassal2 is out
it is importnt that people
can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
- unique version is pure junk and looks like from a tutorial so I can
clean it.
- versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Which version of Roassal are you referring to? Roassal 1 or 2?
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I will work on this then.
Alexandre
On Jun 29, 2014, at 1:02 AM, Tudor Girba tudor@tudorgirba.com wrote:
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
Doru
On Sun, Jun 29, 2014 at 2:14 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
Why Roassal depends on FuelMetalevel?
Because Roassal1 has a feature to export view using Fuel. This was never really used actually.
- having the stable as a baseline is not nice because clients will cry big times.
- there is no correct version and it would be good to use versionner to manage it
and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
unique version is pure junk and looks like from a tutorial so I can clean it.
versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Which version of Roassal are you referring to? Roassal 1 or 2?
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
This is really simple. 2 min to fix. I'm getting fast on that and I can do it. Use Versionner it is cool.
Stef
On 29/6/14 15:23, Alexandre Bergel wrote:
I will work on this then.
Alexandre
On Jun 29, 2014, at 1:02 AM, Tudor Girba tudor@tudorgirba.com wrote:
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
Doru
On Sun, Jun 29, 2014 at 2:14 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
Why Roassal depends on FuelMetalevel?
Because Roassal1 has a feature to export view using Fuel. This was never really used actually.
- having the stable as a baseline is not nice because clients will cry big times.
- there is no correct version and it would be good to use versionner to manage it
and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
unique version is pure junk and looks like from a tutorial so I can clean it.
versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Which version of Roassal are you referring to? Roassal 1 or 2?
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
This is really important to have Roassal1 fully working.
Stef
On Mon, Jun 30, 2014 at 10:38 AM, stepharo stepharo@free.fr wrote:
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
This is really important to have Roassal1 fully working.
Are we not suppose to migrate all the projects using Roassal1 to Roassal2 ? We did some with Anne few weeks ago but I do not have any news of that.
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, in the final Moose 5.0, we should end up with only Roassal2. However, there exist external code that is based on Roassal 1 already, so Roassal 1 should remain clean and loadable separately.
Cheers, Doru
On Mon, Jun 30, 2014 at 10:54 AM, Leo Perard leo.perard@gmail.com wrote:
On Mon, Jun 30, 2014 at 10:38 AM, stepharo stepharo@free.fr wrote:
Stef means Roassal 1.
Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution.
This is really important to have Roassal1 fully working.
Are we not suppose to migrate all the projects using Roassal1 to Roassal2 ? We did some with Anne few weeks ago but I do not have any news of that.
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Cheers, Leo Perard University of Lille 1
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, in the final Moose 5.0, we should end up with only Roassal2. However, there exist external code that is based on Roassal 1 already, so Roassal 1 should remain clean and loadable separately.
+1
Cheers, Doru
On Mon, Jun 30, 2014 at 10:54 AM, Leo Perard <leo.perard@gmail.com mailto:leo.perard@gmail.com> wrote:
On Mon, Jun 30, 2014 at 10:38 AM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote: Stef means Roassal 1. Exactly because Fuel was not used, we can remove this behavior. I guess there is quite some client code that still uses Roassal 1, so, it would still be nice to have a clean version of Roassal 1 even after we remove it from the main Moose distribution. This is really important to have Roassal1 fully working. Are we not suppose to migrate all the projects using Roassal1 to Roassal2 ? We did some with Anne few weeks ago but I do not have any news of that. 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 -- Cheers, Leo Perard University of Lille 1 _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev-- www.tudorgirba.com http://www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Alex
have a look at the configuration because it is not clean. I can fix it.
Why Roassal depends on FuelMetalevel?
Because Roassal1 has a feature to export view using Fuel. This was never really used actually.
- having the stable as a baseline is not nice because clients will cry big times.
- there is no correct version and it would be good to use versionner to manage it
and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
unique version is pure junk and looks like from a tutorial so I can clean it.
versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
Which version of Roassal are you referring to? Roassal 1 or 2?
Re: [Moose-dev] Re: About roassal2
Alexandre
Hi Stef,
You have now access to roassal 1
Alexandre
ok I will have a look.
On 2/7/14 04:00, Alexandre Bergel wrote:
Hi Stef,
You have now access to roassal 1
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jun 28, 2014, at 1:39 PM, stepharo <stepharo@free.fr mailto:stepharo@free.fr> wrote:
Hi alex
Why Roassal depends on FuelMetalevel?
- having the stable as a baseline is not nice because clients will
cry big times.
- there is no correct version and it would be good to use versionner
to manage it and to release some versions from time to time. Now that roassal2 is out it is importnt that people can build on versions if they want.
Typically Synectiquers should really pay attention to this "detail"
- unique version is pure junk and looks like from a tutorial so I can
clean it.
- versionDevelopment: introduce a dependencies to FuelMetalevel.
I do not have access to it but I can clean it fast. Else I will fork it.
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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok I looked at it and Roassal1 was nearly ok. I produced a new stable version with latest image versions including all the packages (Athens and others).
Stef
-
Alexandre Bergel -
Leo Perard -
stepharo -
Tudor Girba