28 Jun
2014
28 Jun
'14
8:33 p.m.
Hi
stable and development points to the same.
Then I do not see why GraphET requires RoassalPdfExporter2 and Neo.
Again this configuration looks to me like a way to load everything.
I think that I will really try another way to manage Moose because I
start to
think that it goes nowhere. This is like the XMLSupport that loaded the
clients like SIXX of XML.
I did XMLParser and XMLWriter and this is much much nicer, smaller, less
complex.
Stef
29 Jun
29 Jun
2:20 a.m.
Cleaning the configuration is indeed important. Now, I am just wondering about your
process, how do you plan to clean all these configuration without breaking the build?
I have no problem to grant you access in Roassal-related software, but it would not be
nice to end up in an unstable version of Moose.
Alternative solution is to build a smalltalkhub repository just for Moose configurations?
Alexandre
On Jun 28, 2014, at 2:33 PM, stepharo <stepharo(a)free.fr> wrote:
Hi
stable and development points to the same.
Then I do not see why GraphET requires RoassalPdfExporter2 and Neo.
Again this configuration looks to me like a way to load everything.
I think that I will really try another way to manage Moose because I start to
think that it goes nowhere. This is like the XMLSupport that loaded the clients like SIXX
of XML.
I did XMLParser and XMLWriter and this is much much nicer, smaller, less complex.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
30 Jun
30 Jun
10:27 a.m.
Since Moose builds on baselines most of the time there is no impact.
Writing a stable is just a way to create a milestone.
I have no problem to fork but if I fork configurations I will also fork
the jenkin jobs
because this is linked and may be people will get frustrated.
On 29/6/14 02:20, Alexandre Bergel wrote:
Cleaning the configuration is indeed important. Now, I
am just wondering about your process, how do you plan to clean all these configuration
without breaking the build?
I have no problem to grant you access in Roassal-related software, but it would not be
nice to end up in an unstable version of Moose.
Alternative solution is to build a smalltalkhub repository just for Moose
configurations?
Alexandre
On Jun 28, 2014, at 2:33 PM, stepharo <stepharo(a)free.fr> wrote:
> Hi
>
> stable and development points to the same.
> Then I do not see why GraphET requires RoassalPdfExporter2 and Neo.
>
> Again this configuration looks to me like a way to load everything.
>
> I think that I will really try another way to manage Moose because I start to
> think that it goes nowhere. This is like the XMLSupport that loaded the clients like
SIXX of XML.
>
> I did XMLParser and XMLWriter and this is much much nicer, smaller, less complex.
> Stef
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
11:13 a.m.
No fork, please. We are too small :)
Doru
On Mon, Jun 30, 2014 at 10:27 AM, stepharo <stepharo(a)free.fr> wrote:
Since Moose builds on baselines most of the time there
is no impact.
Writing a stable is just a way to create a milestone.
I have no problem to fork but if I fork configurations I will also fork
the jenkin jobs
because this is linked and may be people will get frustrated.
On 29/6/14 02:20, Alexandre Bergel wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
Cleaning the configuration is indeed important.
Now, I am just wondering
about your process, how do you plan to clean all these configuration
without breaking the build?
I have no problem to grant you access in Roassal-related software, but it
would not be nice to end up in an unstable version of Moose.
Alternative solution is to build a smalltalkhub repository just for Moose
configurations?
Alexandre
On Jun 28, 2014, at 2:33 PM, stepharo <stepharo(a)free.fr> wrote:
Hi
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
stable and development points to the same.
Then I do not see why GraphET requires RoassalPdfExporter2 and Neo.
Again this configuration looks to me like a way to load everything.
I think that I will really try another way to manage Moose because I
start to
think that it goes nowhere. This is like the XMLSupport that loaded the
clients like SIXX of XML.
I did XMLParser and XMLWriter and this is much much nicer, smaller, less
complex.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12:13 p.m.
No fork, please. We are too small :)
indeed this is why I'm asking people to either give me access and I do
the job or to do the job.
Stef
Doru
On Mon, Jun 30, 2014 at 10:27 AM, stepharo <stepharo(a)free.fr
<mailto:stepharo@free.fr>> wrote:
Since Moose builds on baselines most of the time there is no impact.
Writing a stable is just a way to create a milestone.
I have no problem to fork but if I fork configurations I will also
fork the jenkin jobs
because this is linked and may be people will get frustrated.
On 29/6/14 02:20, Alexandre Bergel wrote:
Cleaning the configuration is indeed important. Now, I am just
wondering about your process, how do you plan to clean all
these configuration without breaking the build?
I have no problem to grant you access in Roassal-related
software, but it would not be nice to end up in an unstable
version of Moose.
Alternative solution is to build a smalltalkhub repository
just for Moose configurations?
Alexandre
On Jun 28, 2014, at 2:33 PM, stepharo <stepharo(a)free.fr
<mailto:stepharo@free.fr>> wrote:
Hi
stable and development points to the same.
Then I do not see why GraphET requires RoassalPdfExporter2
and Neo.
Again this configuration looks to me like a way to load
everything.
I think that I will really try another way to manage Moose
because I start to
think that it goes nowhere. This is like the XMLSupport
that loaded the clients like SIXX of XML.
I did XMLParser and XMLWriter and this is much much nicer,
smaller, less complex.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3828
days inactive
3830
days old
4 comments
3 participants
participants (3)
-
Alexandre Bergel -
stepharo -
Tudor Girba