[Stackless] new releases?
richard.m.tew at gmail.com
Thu Feb 27 21:20:01 CET 2014
Is it safe to push given the new line work done?
My local clone has no custom changes, but orginated from before the
new line fixes. I've since pulled the latest from the repo, is this
enough to make my clone safe to push back?
On 2/24/14, Kristján Valur Jónsson <kristjan at ccpgames.com> wrote:
> I am relatively sure that all stackless changes have been merged between the
> I did a perfunctory diff of the 2.7-slp and 3.2-slp folders, particularly
> the unittests, and it seems everything that has tests is accounted for.
> 3.3-slp follows automatically from that since it is a merge from 3.2-slp
> Are you perhaps speaking of merges from the corresponding cPython branches?
> We can do that, but we then have to be careful about the revisions we pick
> for release.
> As for 3.4, there is no 3.4-slp branch in the repo. I did one such branch
> once, but I forget where it ended up. I understand there is another
> somewhere floating around. but it certainly isn't part of the bitbucket
> repo, unless I'm missing something obvious.
>> -----Original Message-----
>> From: stackless-bounces at stackless.com [mailto:stackless-
>> bounces at stackless.com] On Behalf Of Richard Tew
>> Sent: 23. febrúar 2014 20:40
>> To: The Stackless Python Mailing List
>> Subject: Re: [Stackless] new releases?
>> I'll prepare the 2.7.6 release, and all inbetween up to 3.3.4. If no-one
>> 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
>> it would be appreciated.
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless