Hi,

On Tue, Oct 16, 2012 at 9:58 AM, Nicolas Anquetil <Nicolas.Anquetil@inria.fr> wrote:
On 16/10/12 00:12, Alexandre Bergel wrote:
Yes, I am interested in this!
However the tasks you mentions are highly time consuming...
that's what I was about to say too, there are only 3 issues, but they are not small well defined bug to solve, it's enhancement maintenance at its best.Issue


799: Editing code in Glamour must be faster
Issue 851: Create a stable version for Moose and all its subparts Issue
853: ConfigurationOfMoose should be split to reflect core vs suite

Things that require potentially months of effort ... (in my limited understanding  at least)
not something that you can tackle until the end of the year

I think there is a misunderstanding. These three are rather small tasks. My guess is that they entail some 3 days each.
 
I have been willing to push moosechef for more than a year I think :-(
I will try to put some effort there

Great. This is indeed a large and vague task. Let's synchronize around it and create detailed tasks. Could you propose a small set?
 
Cheers,
Doru



nicolas


Alexandre


On Oct 15, 2012, at 3:28 AM, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi,

We have to think about releasing Moose 4.7 and moving to Pharo 2.0.

There are several reasons why the move to 2.0 would make sense:
1. Athens is coming. We have a major interest in this technology and we need to get on it as soon as possible.
2. The environment moved to RPackage entirely.
3. Pharo needs users.

Before moving to Pharo 2.0, we need to release a robust 4.7. There are still some open points:
http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone%3D4.7

The most pressing ones are:
Issue 799:      Editing code in Glamour must be faster
Issue 851:      Create a stable version for Moose and all its subparts
Issue 853:      ConfigurationOfMoose should be split to reflect core vs suite

Another area to look into is the cleaning of the FAMIX navigation. Right now it's a mess in there. We should probably remove most of the hardcoded methods and rely on Chef. Any taker?

My idea is to target a release this year. Input is more than welcome :)

Cheers,
Doru

--
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

_______________________________________________
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"