[Pandas-dev] 0.11.x maintenance

[Wes McKinney]

I definitely wasn't suggesting 2 released versions, but just wanting
to have a plan in the even that critical bug fixes require a minor
release. Wouldn't want that to prevent significant PRs from getting
merged. Hopefully said critical bug fixes would only require a handful
of cherry-picks on top of the maintenance branch-- IPython has been
doing as much with their minor releases but it definitely is extra
work to have to backport bug fixes.

On Fri, Apr 26, 2013 at 5:48 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>
> aside from xlrd, and the minor HDFStore change (which should go in 0.11.1 in
> any event), I don't think any API changes in current master
>
> why don't we say 1/6wks for 0.11.1...and just try to do bug fixes / avoid
> big API changes
>
> I also would be -1 on mainting 2 released versions.....I think its
> reasonable to just push bigger changes to 0.12 and pull straightforward
> stuff to 0.11.1
>
>
> On Fri, Apr 26, 2013 at 8:37 AM, yoval p. <yoval at gmx.com> wrote:
>>
>> The story is that it was unclear if a bugtrack release
>> is always done, and there is still no milestone for 0.11.1, which
>> is how we're managing issues right now. confusion ensued.
>>
>> So we're doing a 0.11.1 - Obviously a good idea, already
>> some serious bugs fixed.
>>
>> Breaking changes:
>>
>> There are basically 2 breaking changes, requiring
>> to xlrd>=0.9.0 and reworking the repr for various things
>> (Timestamp, *Index() now produce valid python code).
>> Let me know what you want rolled back and deal with it.
>>
>> On the release engineering side of things:
>>
>> I think the wait for 0.11 to be release seriously compromised
>> the development momentum. We did very well scheduling things
>> for 0.12, but then things just got stuck waiting for 0.11rc1 then final
>> and now 0.11.1, I think it's costing pandas too much to do things
>> this way, there's obviously so much just waiting to be done, and PRs
>> are for review, not for stagnation.
>> As a special concern, this sort of things reduces jeff's output to a
>> meager 20 PRs per day which is just net loss as far as pandas is
>> concerned.
>>
>> OTOH maintaining multiple maintenance branches is extra work
>> and makes the history more complex. There are alternative
>> git workflows (gitflow, github are the usual fare), would be
>> glad to hear opinions on what would work best.
>>
>>
>> Please create a GH milestone for 0.11.1, and set the time-frame
>> for it.
>>
>> Let me know if you want something rolled back for 0.11.1.
>>
>> Yoval
>>
>> On 04/26/2013 04:52 AM, Wes McKinney wrote:
>> > hey folks,
>> >
>> > what is the story with 0.12.x? Are we breaking any APIs yet? If so we
>> > should probably plan for a 0.11.1 that is *bugfix *only and we
>> > somewhat diligent about backporting critical bugfixes. Let me know
>> > what you think.
>> >
>> > - Wes
>> > _______________________________________________
>> > Pandas-dev mailing list
>> > Pandas-dev at python.org
>> > http://mail.python.org/mailman/listinfo/pandas-dev
>> >
>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> http://mail.python.org/mailman/listinfo/pandas-dev
>
>
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> http://mail.python.org/mailman/listinfo/pandas-dev
>