Hi
what is the process to get changes integrated into moose? We fixed two problems in DM and knonkrator and I do not know what is the process for their integration. Then is the rest API integrated into Moose? Stef _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Just commit. If the package is in the config it will get loaded in the next build. In Moose, we used an optimistic strategy until now.
Doru Sent from my iPhone On Apr 4, 2014, at 9:55, Pharo4Stef <[hidden email]> wrote: > Hi > > what is the process to get changes integrated into moose? > We fixed two problems in DM and knonkrator and I do not know > what is the process for their integration. > > Then is the rest API integrated into Moose? > > Stef > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
The rest api is not integrated because it is/was too crude.
Doru Sent from my iPhone On Apr 4, 2014, at 11:00, Tudor Girba <[hidden email]> wrote: > Just commit. If the package is in the config it will get loaded in the next build. In Moose, we used an optimistic strategy until now. > > Doru > > Sent from my iPhone > > On Apr 4, 2014, at 9:55, Pharo4Stef <[hidden email]> wrote: > >> Hi >> >> what is the process to get changes integrated into moose? >> We fixed two problems in DM and knonkrator and I do not know >> what is the process for their integration. >> >> Then is the rest API integrated into Moose? >> >> Stef >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Tudor Girba-2
On 04 Apr 2014, at 11:00, Tudor Girba <[hidden email]> wrote: > Just commit. If the package is in the config it will get loaded in the next build. In Moose, we used an optimistic strategy until now. So I do not get why the package version that andre published was not loaded (and his changes looked to me wrong). > > Doru > > Sent from my iPhone > > On Apr 4, 2014, at 9:55, Pharo4Stef <[hidden email]> wrote: > >> Hi >> >> what is the process to get changes integrated into moose? >> We fixed two problems in DM and knonkrator and I do not know >> what is the process for their integration. >> >> Then is the rest API integrated into Moose? >> >> Stef >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by pharo4Stef@free.fr
>
> Then is the rest API integrated into Moose? you did not reply to the second question? Synectique payed vincent to develop a rest api for moose and we/they could keep it for themselves. Now if moose is not interested by this package it would be good to know it. Else action should be taken. Stef > > Stef > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Tudor Girba-2
On 04 Apr 2014, at 11:04, Tudor Girba <[hidden email]> wrote: > The rest api is not integrated because it is/was too crude. what do you mean that too crude? When did you send feedback? > > Doru > > Sent from my iPhone > > On Apr 4, 2014, at 11:00, Tudor Girba <[hidden email]> wrote: > >> Just commit. If the package is in the config it will get loaded in the next build. In Moose, we used an optimistic strategy until now. >> >> Doru >> >> Sent from my iPhone >> >> On Apr 4, 2014, at 9:55, Pharo4Stef <[hidden email]> wrote: >> >>> Hi >>> >>> what is the process to get changes integrated into moose? >>> We fixed two problems in DM and knonkrator and I do not know >>> what is the process for their integration. >>> >>> Then is the rest API integrated into Moose? >>> >>> Stef >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by pharo4Stef@free.fr
On 04 Apr 2014, at 09:55, Pharo4Stef <[hidden email]> wrote: > Hi > > what is the process to get changes integrated into moose? > We fixed two problems in DM and knonkrator and I do not know > what is the process for their integration. So I do not get why the package version that andre published was not loaded (and his changes looked to me wrong so this is even worse). > > Then is the rest API integrated into Moose? > > Stef > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
I did reply :).
It was not integrated because it was (I do not know the current status because nobody promotes it anymore) too crude at that time. Doru On Sat, Apr 5, 2014 at 9:08 AM, Pharo4Stef <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by pharo4Stef@free.fr
Of course I did. Doru On Sat, Apr 5, 2014 at 9:08 AM, Pharo4Stef <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Stéphane Ducasse
Which is the package? Doru On Sat, Apr 5, 2014 at 9:06 AM, Stéphane 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 |
I imagine that this is DistributionMap. It was not on my machine.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On Sat, Apr 5, 2014 at 12:20 PM, Stéphane Ducasse <[hidden email]> wrote:
Hello Stef, 1) You are referring Moose-DistributionMap-AndreHora.52. I don't understand why it was not integrated in your image.
For example, I committed Moose-DistributionMap-AndreHora.53 and (as the package DistributionMap is in the config) the change is already integrated in last Moose image [1] as Doru said. 2) You said that the change "Compiler evaluate: -> Smalltalk evaluate:" is wrong.
Ok, I can do the rollback. But it was mined from Pharo 2.0 -> 3.0, and currently in Pharo there are many Smalltalk evaluate:
Let me know which one is correct, or maybe it depends of the context? [1] https://ci.inria.fr/moose/view/Moose%205.0/job/moose-5.0/lastSuccessfulBuild/artifact/moose-5.0.zip
Andre Hora _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
can you send a mail to the pharo mailing-list reporting that? Because this is ugly.
Smalltalk should not have evaluate: just Compiler evaluate:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
I agree with that :) Doru On Sat, Apr 5, 2014 at 4:06 PM, Stéphane 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 |
In reply to this post by Tudor Girba-2
Hi Doru, On Sat, Apr 5, 2014 at 9:27 AM, Tudor Girba <[hidden email]> wrote: If you could identify concretely what is missing in it (architecture, features etc.) it can be good. We are using it to build our web infrastructure and so far we've exposed through it whatever is needed from a moose model. Regards, _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi, I think the thing should be the other way around. You announced an alpha a long time ago including a web ui prototype. Me and others took a look at it, and there was some discussion on the mailing list. And then silence. It's hard to keep track of what is going on without proactive communication.
I would suggest that you provide everyone with an overview of what exists and then we go from there. Doru On Mon, Apr 7, 2014 at 7:55 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 |
In reply to this post by Stéphane Ducasse
On Sat, Apr 5, 2014 at 4:06 PM, Stéphane Ducasse <[hidden email]> wrote:
yes.. may be :)
sure!
Andre Hora _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |