short bug fixing period
Locked
 
|
Hi,
I would like to allow a short period of about 1-2 weeks for bug fixing before we move to Pharo 3.0. So, in case you notice a problem, please report it as soon as possible. Once we move to Pharo 3.0, we will no longer support Pharo 2.0 for bug fixes.
Cheers, Doru _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Hola,
There are some bugs in Roassal, including a memory leak. I told Alex about it 2 days ago but I guess he is a bit busy right now ;-). I think some of these should be addressed before moving to 3.0. On Sep 13, 2013, at 5:45 AM, Tudor Girba <[hidden email]> wrote: > Hi, > > I would like to allow a short period of about 1-2 weeks for bug fixing before we move to Pharo 3.0. > > So, in case you notice a problem, please report it as soon as possible. Once we move to Pharo 3.0, we will no longer support Pharo 2.0 for bug fixes. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Well... First we need to make sure the issue is not rooted in AspectMaps :-)
Moving to 3.0 is more about the underlying runtime, I am not sure this impact the memory leak you mention. Alexandre On Sep 13, 2013, at 2:00 PM, Johan Fabry <[hidden email]> wrote: > Hola, > > There are some bugs in Roassal, including a memory leak. I told Alex about it 2 days ago but I guess he is a bit busy right now ;-). I think some of these should be addressed before moving to 3.0. > > On Sep 13, 2013, at 5:45 AM, Tudor Girba <[hidden email]> wrote: > >> Hi, >> >> I would like to allow a short period of about 1-2 weeks for bug fixing before we move to Pharo 3.0. >> >> So, in case you notice a problem, please report it as soon as possible. Once we move to Pharo 3.0, we will no longer support Pharo 2.0 for bug fixes. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > 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 |
|
|
In reply to this post by jfabry
What exactly is the issue? Please report this publicly to maximize the chances of a fix, and to everyone informed. Doru On Fri, Sep 13, 2013 at 2:00 PM, Johan Fabry <[hidden email]> wrote: Hola, "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
I'm very sorry, I have been too busy with family issues to be able to make a proper bug report. I only talked to Alex about it using the context of an existing conversation. I hope to find some time this weekend to investigate how to reproduce it outside of this context.
On Sep 13, 2013, at 9:18 AM, Tudor Girba <[hidden email]> wrote: > What exactly is the issue? > > Please report this publicly to maximize the chances of a fix, and to everyone informed. > > Doru > > > On Fri, Sep 13, 2013 at 2:00 PM, Johan Fabry <[hidden email]> wrote: > Hola, > > There are some bugs in Roassal, including a memory leak. I told Alex about it 2 days ago but I guess he is a bit busy right now ;-). I think some of these should be addressed before moving to 3.0. > > On Sep 13, 2013, at 5:45 AM, Tudor Girba <[hidden email]> wrote: > > > Hi, > > > > I would like to allow a short period of about 1-2 weeks for bug fixing before we move to Pharo 3.0. > > > > So, in case you notice a problem, please report it as soon as possible. Once we move to Pharo 3.0, we will no longer support Pharo 2.0 for bug fixes. > > > > Cheers, > > Doru > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ 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 |