I'll prepare the 2.7.6 release, and all inbetween up to 3.3.4. If no-one has updated 3.4 after that, I'll prepare a release for that.
But if you want to ensure all merges are present, before I get around to that, it would be appreciated. Cheers, Richard. On 2/23/14, Kristján Valur Jónsson <[email protected]> wrote: > I've finished grafting 2.7 changes to 3.2 and merging to 3.3 > > Now, what about 3.4 :) > > > > > > K > > ________________________________ > From: [email protected] [[email protected]] on > behalf of Kristján Valur Jónsson [[email protected]] > Sent: Monday, February 17, 2014 21:01 > To: The Stackless Python Mailing List > Subject: Re: [Stackless] new releases? > > Also mkII would get my vote :-) > > > Sent from the æther. > > -------- Original message -------- > From: Richard Tew > Date:17/02/2014 18:50 (GMT+00:00) > To: The Stackless Python Mailing List > Subject: Re: [Stackless] new releases? > > Sure. How should we version number it? "2.7.6slp2"? > > Also, is there an easy way to work out what needs to be done to get > 3.x up to date? > > Richard. > > On Tue, Feb 18, 2014 at 12:29 AM, Kristján Valur Jónsson > <[email protected]> wrote: >> So, with the latest burst of activity, I wonder if it is time to redo the >> release? >> >> We have restored binary compatibility with Cpython and so pyside and qt >> should now work. >> >> K >> >> >> _______________________________________________ >> Stackless mailing list >> [email protected] >> http://www.stackless.com/mailman/listinfo/stackless > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless > > _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
