On Tue, Feb 19, 2013 at 9:14 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote;wrote:
the symbolic version #bleedingEdge should not be
defined. There no point
on create a special version to load latest packages, metacello does that
work by default: if you call version #bleedingEdge, it takes the latest
baseline and load latest packages defined there.
Ok. I didn't know about the existence of default convention in metacello.
But, for me, bleedingEdge is more explicit about its task: fetching all the
latest packages for a given baseline.
Esteban
On Feb 19, 2013, at 8:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi Usman,
Great.
But, the #bleedingEdge version should be named #development.
Cheers,
Doru
On Mon, Feb 18, 2013 at 11:21 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;wrote:
I sent this mail yesterday but strangely no
received it, so here it is
again.
With Nicolas, we have created a first baseline of Moose based on the
projects in STHub. The baseline baseline47STHub: corresponds to the old
core-default baseline.
Loading the baseline on 1.4 works fine, here are the test results:
998 run, 991 passes, 1 expected failures, 6 failures, 0 errors, 0
unexpected passes
For each proj moved to SThub, we have tried to define two symbolic
versions:
#stable: a specific version of a proj at the time of move to STHub
#bleedingEdge: load the latest packages of a proj.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)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(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev