GraphET2
Locked
 
|
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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
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 <[hidden email]> 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 > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
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 <[hidden email]> 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 >> [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 |
|
|
No fork, please. We are too small :) Doru On Mon, Jun 30, 2014 at 10:27 AM, stepharo <[hidden email]> wrote: Since Moose builds on baselines most of the time there is no impact. "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
indeed this is why I'm asking people to either give me access and I do the job or to do the job. Stef
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |