About 1.2 beta

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

About 1.2 beta

Stéphane Ducasse
Hi guys

We would like to go beta for the end of the week or beginning/end of next week.
It would gives us one month or two to produce 1.2.
So we could have 1.2 for the beginning of the year.
We could start 1.3 unstable around end of Nov.
What do you think?



Stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: About 1.2 beta

Mariano Martinez Peck


On Wed, Oct 27, 2010 at 12:39 PM, Stéphane Ducasse <[hidden email]> wrote:
Hi guys

We would like to go beta for the end of the week or beginning/end of next week.
It would gives us one month or two to produce 1.2.

Yes. Remember that several external packages used in PharoDev need updates to work in 1.2, so we need time for that.
 
So we could have 1.2 for the beginning of the year.
We could start 1.3 unstable around end of Nov.
What do you think?


agree.
 
are there critical bugs pending for 1.2?



Stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: About 1.2 beta

Schwab,Wilhelm K
In reply to this post by Stéphane Ducasse
Stef,

It would be nice to tackle 2476 (ConnectionQueue) and 1057 (named serial ports).  I have what might be better called improvements than fixes.  For 1057, the comments suggest that I might be fairly far off, having dealt only with getting the code to work.  The way the vm (Linux at least) is designed, I don't see an elegant solution.  I would have expected that opening a named port would produce a descriptor and that reads and writes would be initiated using the latter, but the vm holds onto that, so one passes port number/name to every call; if anything, it "thinks" in terms of names.

Bill



________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Stéphane Ducasse [[hidden email]]
Sent: Wednesday, October 27, 2010 6:39 AM
To: [hidden email] Development
Subject: [Pharo-project] About 1.2 beta

Hi guys

We would like to go beta for the end of the week or beginning/end of next week.
It would gives us one month or two to produce 1.2.
So we could have 1.2 for the beginning of the year.
We could start 1.3 unstable around end of Nov.
What do you think?



Stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project