- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
2.9.0.2 schedule?
Thu, 2011-05-26, 15:59
Is there an intention to release a 2.9.0.2 in the near future? Or anywhere I can go to see when (or whether) there will be such a release and what will be in it?
I'm particularly concerned about https://issues.scala-lang.org/browse/SI-4642: essentially using an immutable Set for very large collections which are regularly updated has become impossible; I realise that the issue hasn't got many votes but I would place this as pretty critical; much more so that the immutable.Map.keySet issue which could be worked around without *totally* changing ones application.
For example, a class which contains an internal immutable Set which is frequently updated and "passed" to other parts of the program across thread boundaries is now essentially *completely broken* with no workaround that I can see (the issue effects immutable.TreeSet as well, I believe).
Chris
I'm particularly concerned about https://issues.scala-lang.org/browse/SI-4642: essentially using an immutable Set for very large collections which are regularly updated has become impossible; I realise that the issue hasn't got many votes but I would place this as pretty critical; much more so that the immutable.Map.keySet issue which could be worked around without *totally* changing ones application.
For example, a class which contains an internal immutable Set which is frequently updated and "passed" to other parts of the program across thread boundaries is now essentially *completely broken* with no workaround that I can see (the issue effects immutable.TreeSet as well, I believe).
Chris
Thu, 2011-05-26, 17:17
#2
Re: 2.9.0.2 schedule?
On Thu, May 26, 2011 at 11:59, Chris Marshall wrote:
> become impossible; I realise that the issue hasn't got many votes but I
Actually, I think 4 votes in such a short time (and 6 watchers) is
quite a deal. Most issues linger unvoted for.
Thu, 2011-05-26, 17:27
#3
Re: 2.9.0.2 schedule?
Especially given that Jira is a fairly new installation...
On 26 May 2011 17:10, Daniel Sobral <dcsobral@gmail.com> wrote:
--
Kevin Wright
gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda
"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra
On 26 May 2011 17:10, Daniel Sobral <dcsobral@gmail.com> wrote:
On Thu, May 26, 2011 at 11:59, Chris Marshall <oxbowlakes@gmail.com> wrote:
> become impossible; I realise that the issue hasn't got many votes but I
Actually, I think 4 votes in such a short time (and 6 watchers) is
quite a deal. Most issues linger unvoted for.
--
Daniel C. Sobral
I travel to the future all the time.
--
Kevin Wright
gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda
"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra
Thu, 2011-05-26, 17:37
#4
Re: 2.9.0.2 schedule?
It was on 1 vote when I wrote the email, I think
On Thu, May 26, 2011 at 5:10 PM, Daniel Sobral <dcsobral@gmail.com> wrote:
On Thu, May 26, 2011 at 5:10 PM, Daniel Sobral <dcsobral@gmail.com> wrote:
On Thu, May 26, 2011 at 11:59, Chris Marshall <oxbowlakes@gmail.com> wrote:
> become impossible; I realise that the issue hasn't got many votes but I
Actually, I think 4 votes in such a short time (and 6 watchers) is
quite a deal. Most issues linger unvoted for.
--
Daniel C. Sobral
I travel to the future all the time.
On Thu, May 26, 2011 at 4:59 PM, Chris Marshall <oxbowlakes@gmail.com> wrote:
We don't like to do hotfixes. It would be much better to avoid them, so there's no release schedule for future hotfix releases. The problem you raise looks so bad that it would almost certainly have been rolled into the previous fix if we had known about it in time. We'll see what we can do about it, and will report once we have a plan.
-- Martin