13 Nov
2011
13 Nov
'11
9:20 p.m.
Hi,
On 13 Nov 2011, at 09:02, Stéphane Ducasse wrote:
we do not lose anything if we have a clear process.
Right now I have no idea what is the process.
And just publishing a package and thinking that it will be loaded leads to the fact that
we cannot load moose anymore.
This is because of the mess introduced by having hardcoded versions during development.
There is nothing like a free lunch and we could script
metacello to generate support our process.
It makes me smile because we say that we are tool builder and we still do not script the
API of metacello.
You wrote a chapter on Metacello. So, you are a great candidate for providing the support
:).
Cheers,
Doru
Stef
--
www.tudorgirba.com
"When people care, great things can happen."
This is precisely the problem I was referring to
when I said that it is not clear what is the best solution when versioning Moose with
Metacello. What we do not want is lose versions like this along the way.
Cheers,
Doru
On 8 Nov 2011, at 19:08, Usman Bhatti wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev We udpated the configuration of merlin
So that satble in 1.5 and development is 1.6 and 1.6 contains our changes
On Tue, Nov 8, 2011 at 6:33 PM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
to have a default select: [:each | 'pac*' match
and to avoid to have ' in drop box and this is not in the latest version of moose.
How do we know merge process work in moose?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Beauty is where we see it."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev