config of moose on SThub
Locked
 
|
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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Hi Usman, Great. But, the #bleedingEdge version should be named #development. Cheers, Doru
On Mon, Feb 18, 2013 at 11:21 PM, Usman Bhatti <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
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.
Esteban On Feb 19, 2013, at 8:37 AM, Tudor Girba <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
On Tue, Feb 19, 2013 at 9:14 AM, Esteban Lorenzano <[hidden email]> wrote:
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.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: config of moose on SThub
|
|
Usman
we should follow what is there else this will be the mess. Add a comment starting what it loads and we are done. I think that this is probably written in the chapter I wrote so this is not even that there is no documentation. Stef On Feb 19, 2013, at 9:24 AM, Usman Bhatti <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
+1 Usman, could you take care of this? Doru On Wed, Feb 20, 2013 at 9:21 AM, stephane ducasse <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
On Wed, Feb 20, 2013 at 1:17 PM, Tudor Girba <[hidden email]> wrote:
I'll look it tomorrow.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by stephane ducasse
On Wed, Feb 20, 2013 at 9:21 AM, stephane ducasse <[hidden email]> wrote:
As discussed with Stef, it is proposed that we have two symbolic versions for each project of Moose: - #development point to a baseline and gets the latest packages of a project
- #stable is created/updated for every project every time we have a new release of Moose. I'll update the configs tomorrow and start loading things on 2.0. usman
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Great. Doru On Thu, Feb 21, 2013 at 10:53 AM, Usman Bhatti <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |