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 <jfabry@dcc.uchile.cl> 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 <tudor@tudorgirba.com> 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
> Moose-dev@iam.unibe.ch
> 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
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"