Hi,
On 13 Nov 2011, at 22:10, Stéphane Ducasse wrote:
I do not understand the moose process.
What is so difficult to understand? Anytime we can, we load the latest development version (or default how we called it first). If one is not provided, we load some version, like in the case of Merlin.
If we cannot control how fixes get introduced in the system and the only solution is to fork then I will fork but this is suboptimal. Ok I will do it then.
I do not understand.
Doru
Stef
We have absolutely no support for branching other than using a separate Monticello repository and handling the branched code manually.
It worked reasonably well until now.
I will stress it again. We do need better configuration support, but we need effort spent in this direction, too :).
Cheers, Doru
On 13 Nov 2011, at 16:23, Stéphane Ducasse wrote:
Hi
this is still totally unclear to me how I can change Moose and get my changes not breaking parts of moose that I do not know or are not loaded?
I want to work on the importer/extractor proposal I sent around last week. So I can implement the changes but what is the process?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"To utilize feedback, you first have to acquire it."
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
"Speaking louder won't make the point worthier."