19 Jul
2016
19 Jul
'16
1:32 a.m.
Hi Stef,
I am sorry you feel this way. I did not expedite you, only we had exactly these
conversations before.
Like now, the issue was that if we work on the last version of Pharo the code will be
unstable and we will get problems. It turns out that we did not. Where are the signs you
see this as being problematic?
In fact the problem is the opposite. Right now, Moose is unstable because we do not have
the infrastructure and man power to develop in Pharo 5 and 6 at the same time, and we get
conflicting changes especially given that GT are central to both Pharo and Moose. We had
the same issue last year. So, right now we are in consolidation, but afterwards, we have
to move on.
As for selling, if I understand correctly, Synectique builds on the version of Moose that
is stable (5.1), which was released about 1 year ago. Now, it is one year later and we
should release again.
I really do not see the problem.
Cheers,
Doru
On Jul 18, 2016, at 3:55 PM, stepharo
<stepharo(a)free.fr> wrote:
Ok doru. I see that there are no real discussion possible. Sadly Moose became more and
more an ui experimentation platform
versus an analysis platform (this is long time ago that I did not see new analyses beside
MooseChef).
Late 2016, we will have an engineer to work on the core of Moose (meta model and more)
and I will have to think what we will do because
I do not think that I'm really welcomed in the Moose system anymore. Each time I sent
a mail I feel like an idiot telling something wrong.
It is ok and it is probably time for me to step back from Moose and build something else
with less strings attached.
Too bad I thought that Moose was to make sure that people can sell product around it.
Stef
--
www.tudorgirba.com
www.feenk.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
Hi,
We will release Moose soon. The main open issue is the often crashing Roassal, and as
there was some new input recently, I decided to wait a bit for the release.
So, Moose 6.0 release will be on top of Pharo 5.0. After that, the development version of
Moose will move to Pharo 6.0.
Cheers,
Doru
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev On Jul 8, 2016, at 1:20 PM, Usman Bhatti
<usman.bhatti(a)gmail.com> wrote:
Currently, moose provides two possibilities: stable for pharo release and development for
pharo alpha. We have builds for both on the jenkins.
On Fri, Jul 8, 2016 at 12:13 PM, stepharo <stepharo(a)free.fr> wrote:
But why Moose should be using an alpha version of Pharo?
Some people need stable versions of Moose, so moving to Pharo 60 is the best way to make
them fork.
I do not know what ussman thinks about that, but I do not think that it is wise to ship
Pharo60 to synectique clients
so if this is the case I will advise them to fork everything to be able to use Pharo 50.
Now people should not complain after that it is difficult to make people share what there
are doing.
Stef
Le 29/6/16 à 00:24, Alexandre Bergel a écrit :
Hi!
Does the moose build uses Pharo 6? It does not look like…
How to make Moose loads in Pharo 6?
Alexandre
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
--
www.tudorgirba.com
www.feenk.com
"Every thing has its own flow."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev