2014-03-27 12:21 GMT-03:00 Esteban Lorenzano <[email protected]>: > On 27 Mar 2014, at 12:14, Sven Van Caekenberghe <[email protected]> wrote: >> On 27 Mar 2014, at 15:46, Esteban A. Maringolo <[email protected]> wrote:
>>> Will the fix be available for Pharo 2 builds as well? >> >> I knew you were going to ask that, but I don't know. The whole Chronology >> package was changed quite a lot going from 2.0 -> 3.0 >> >> On the other hand, my changes are pretty comprehensible (a couple of >> methods), somebody could certainly try to backport them - but no guarantees >> they will work though. > > pharo3 is at the corner to be out. > we are not integrating/backporting changes to pharo2 since... well, like 6 > months. > so no, it will not be there and it will not be integrated. What is the support strategy for stable versions? Pharo 3 is still beta/release-candidate, so... strictly speaking Pharo 2 is the official stable version. Shouldn't it get support as such? If resource scarcity rules here, I'll understand. > said so... anyone can do their own backport and put it for others in a meta > repo :) It will be so. :) Esteban A. Maringolo
