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
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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch 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 tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 04 Apr 2014, at 11:04, Tudor Girba tudor@tudorgirba.com 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 tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Of course I did.
Doru
On Sat, Apr 5, 2014 at 9:08 AM, Pharo4Stef pharo4Stef@free.fr wrote:
On 04 Apr 2014, at 11:04, Tudor Girba tudor@tudorgirba.com 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 tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse stephane.ducasse@inria.frwrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I imagine that this is DistributionMap. It was not on my machine.
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse stephane.ducasse@inria.fr wrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Sat, Apr 5, 2014 at 12:20 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
I imagine that this is DistributionMap. It was not on my machine.
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...
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Sat, Apr 5, 2014 at 12:20 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote: I imagine that this is DistributionMap. It was not on my machine.
Hello Stef,
- 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.
May be it was an old image.
- 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:
really so it sucks can you send a mail to the pharo mailing-list reporting that? Because this is ugly.
Let me know which one is correct, or maybe it depends of the context?
Smalltalk should not have evaluate: just Compiler evaluate:
[1] https://ci.inria.fr/moose/view/Moose%205.0/job/moose-5.0/lastSuccessfulBuild...
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse stephane.ducasse@inria.fr wrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch 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 stephane.ducasse@inria.frwrote:
On Sat, Apr 5, 2014 at 12:20 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
I imagine that this is DistributionMap. It was not on my machine.
Hello Stef,
- 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.
May be it was an old image.
- 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:
really so it sucks can you send a mail to the pharo mailing-list reporting that? Because this is ugly.
Let me know which one is correct, or maybe it depends of the context?
Smalltalk should not have evaluate: just Compiler evaluate:
[1] https://ci.inria.fr/moose/view/Moose%205.0/job/moose-5.0/lastSuccessfulBuild...
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Sat, Apr 5, 2014 at 4:06 PM, Stéphane Ducasse stephane.ducasse@inria.frwrote:
On Sat, Apr 5, 2014 at 12:20 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
I imagine that this is DistributionMap. It was not on my machine.
Hello Stef,
- 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.
May be it was an old image.
yes.. may be :)
- 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:
really so it sucks can you send a mail to the pharo mailing-list reporting that? Because this is ugly.
sure!
Let me know which one is correct, or maybe it depends of the context?
Smalltalk should not have evaluate: just Compiler evaluate:
[1] https://ci.inria.fr/moose/view/Moose%205.0/job/moose-5.0/lastSuccessfulBuild...
Which is the package?
Doru
On Sat, Apr 5, 2014 at 9:06 AM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
On 04 Apr 2014, at 11:00, Tudor Girba tudor@tudorgirba.com 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 pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 04 Apr 2014, at 09:55, Pharo4Stef pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch 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 pharo4Stef@free.fr wrote:
On 04 Apr 2014, at 09:55, Pharo4Stef pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Doru,
On Sat, Apr 5, 2014 at 9:27 AM, Tudor Girba tudor@tudorgirba.com wrote:
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.
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. Vincent also created Moose Panel as a show case app. Although not actively developed, Vincent keeps vigilant eye on its evolution that helps keeping things on the right track and Kevin fixes/adds things from time to time.
Regards, Usman
Doru
On Sat, Apr 5, 2014 at 9:08 AM, Pharo4Stef pharo4Stef@free.fr wrote:
On 04 Apr 2014, at 09:55, Pharo4Stef pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch 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 usman.bhatti@gmail.com wrote:
Hi Doru,
On Sat, Apr 5, 2014 at 9:27 AM, Tudor Girba tudor@tudorgirba.com wrote:
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.
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. Vincent also created Moose Panel as a show case app. Although not actively developed, Vincent keeps vigilant eye on its evolution that helps keeping things on the right track and Kevin fixes/adds things from time to time.
Regards, Usman
Doru
On Sat, Apr 5, 2014 at 9:08 AM, Pharo4Stef pharo4Stef@free.fr wrote:
On 04 Apr 2014, at 09:55, Pharo4Stef pharo4Stef@free.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Andre Hora -
Pharo4Stef -
Stéphane Ducasse -
Tudor Girba -
Usman Bhatti