Re: [Pharo-dev] PetitParser in 3.0?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-dev] PetitParser in 3.0?

EstebanLM
Hi,

This is a question for the moosers :)
Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella?

cheers, 
Esteban

On 18 Jul 2014, at 10:00, [hidden email] wrote:

I load it from the moose team on sth. Works for me, browser included.

Le 18 juil. 2014 09:24, "Tudor Girba" <[hidden email]> a écrit :
In the case of Moose, #development and #bleedingEdge are the same.

Doru


On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <[hidden email]> wrote:
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.

Norbert

Am 18.07.2014 um 05:21 schrieb Tudor Girba <[hidden email]>:

It loads #development as any CI job should do.

Doru


On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <[hidden email]> wrote:
Stephan Eggermont wrote
Interesting. I wonder what the ci is loading, because if I try to load the
default group in Pharo 3.0, I get an error (hence I load 'Core' and have no
problems)



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.




--

"Every thing has its own flow"



--

"Every thing has its own flow"


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-dev] PetitParser in 3.0?

Tudor Girba-2
Because nobody did it.

Doru


On Fri, Jul 18, 2014 at 12:04 PM, Esteban Lorenzano <[hidden email]> wrote:
Hi,

This is a question for the moosers :)
Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella?

cheers, 
Esteban

On 18 Jul 2014, at 10:00, [hidden email] wrote:

I load it from the moose team on sth. Works for me, browser included.

Le 18 juil. 2014 09:24, "Tudor Girba" <[hidden email]> a écrit :
In the case of Moose, #development and #bleedingEdge are the same.

Doru


On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <[hidden email]> wrote:
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.

Norbert

Am 18.07.2014 um 05:21 schrieb Tudor Girba <[hidden email]>:

It loads #development as any CI job should do.

Doru


On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <[hidden email]> wrote:
Stephan Eggermont wrote
Interesting. I wonder what the ci is loading, because if I try to load the
default group in Pharo 3.0, I get an error (hence I load 'Core' and have no
problems)



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.




--

"Every thing has its own flow"



--

"Every thing has its own flow"




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev