13 Nov
2011
13 Nov
'11
11:07 p.m.
On Nov 13, 2011, at 10:25 PM, Tudor Girba wrote:
since the release cycle of Moose is long and since people use the latest version of Moose
it means that this is difficult to introduce large changes. This is probably ok because it
forces you to get a working system
but if I do a change that touches several packages and one of them does not get loaded or
merged then we are in a mess.
This is what I mean by how fixes get introduced.
In pharo we can **always** rollback in a couple of minutes! Just removing one line in a
file and publishing it and
we are safe and nobody gets impacted.
In Moose no way we can do that. So this is more stress for committers so less people will
improve the core.
Stef
Hi,
On 13 Nov 2011, at 22:10, Stéphane Ducasse wrote:
with merlin this is not the latest since we have to modify the configurationOfMerlin to
point to the latest version.
But anyway
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.