From yoval at gmx.com  Thu Jan  2 03:59:57 2014
From: yoval at gmx.com (yoval p.)
Date: Thu, 02 Jan 2014 04:59:57 +0200
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
Message-ID: <52C4D62D.5050303@gmx.com>

0.13.0 was Tagged yesterday.

Ping me when the binaries are up and I'll send out the ANN
to the ml.

Y

On 12/30/2013 06:49 PM, Wes McKinney wrote:
> hi YP,
> 
> Please go ahead and tag the release. Either you or Jeff should
> announce the release on the usual channels once the binaries make it
> through the tubes to PyPI. We'll be back in the office on 1/3 and can
> do it then.
> 
> cheers and happy new year
> Wes
> 

From jeffreback at gmail.com  Fri Jan  3 17:21:21 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Fri, 3 Jan 2014 11:21:21 -0500
Subject: [Pandas-dev] joris
Message-ID: <1911FC7A-AB50-4ADA-B40A-E1DD8DA40686@gmail.com>


I think jorisvandenbossche
would be nice to add ability to push to master

has done tremendous work with docs (and other PRs)

Jeff


From jtratner at gmail.com  Fri Jan  3 17:38:02 2014
From: jtratner at gmail.com (Jeffrey Tratner)
Date: Fri, 3 Jan 2014 08:38:02 -0800
Subject: [Pandas-dev] joris
In-Reply-To: <1911FC7A-AB50-4ADA-B40A-E1DD8DA40686@gmail.com>
References: <1911FC7A-AB50-4ADA-B40A-E1DD8DA40686@gmail.com>
Message-ID: <CAEgxMcncqquGKRfnmENcQoWD_j30nj_Ls5pzQr8aoKaA+JuL7Q@mail.gmail.com>

+1


On Fri, Jan 3, 2014 at 8:21 AM, Jeff Reback <jeffreback at gmail.com> wrote:

>
> I think jorisvandenbossche
> would be nice to add ability to push to master
>
> has done tremendous work with docs (and other PRs)
>
> Jeff
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140103/d9d9c841/attachment.html>

From wesmckinn at gmail.com  Fri Jan  3 17:45:51 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Fri, 3 Jan 2014 08:45:51 -0800
Subject: [Pandas-dev] joris
In-Reply-To: <1911FC7A-AB50-4ADA-B40A-E1DD8DA40686@gmail.com>
References: <1911FC7A-AB50-4ADA-B40A-E1DD8DA40686@gmail.com>
Message-ID: <CAJPUwMCgEwfkST_u4dUpBNB5da=W+oaZAO62_y0r18bmi8tK6A@mail.gmail.com>

Consider it so. Happy new year everyone

On Fri, Jan 3, 2014 at 8:21 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>
> I think jorisvandenbossche
> would be nice to add ability to push to master
>
> has done tremendous work with docs (and other PRs)
>
> Jeff
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

From jeffreback at gmail.com  Fri Jan  3 17:55:17 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Fri, 3 Jan 2014 11:55:17 -0500
Subject: [Pandas-dev] Fwd:  joris
References: <CAJPUwMCgEwfkST_u4dUpBNB5da=W+oaZAO62_y0r18bmi8tK6A@mail.gmail.com>
Message-ID: <856D71AF-D25A-4AF5-A31D-544449122D0E@gmail.com>

joris

shortly you should have ability to push to master!

I think that you have been putting up quality PRs and very nicely commenting in others

welcome to the team

you might need to subscribe to pandas-dev ml (not sure how that gets added)

Jeff 

Begin forwarded message:

> From: Wes McKinney <wesmckinn at gmail.com>
> Date: January 3, 2014 at 11:45:51 AM EST
> To: Jeff Reback <jeffreback at gmail.com>
> Cc: "pandas-dev at python.org" <pandas-dev at python.org>
> Subject: Re: [Pandas-dev] joris
> 
> Consider it so. Happy new year everyone
> 
>> On Fri, Jan 3, 2014 at 8:21 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>> 
>> I think jorisvandenbossche
>> would be nice to add ability to push to master
>> 
>> has done tremendous work with docs (and other PRs)
>> 
>> Jeff
>> 
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140103/9de3ed0b/attachment.html>

From cpcloud at gmail.com  Fri Jan  3 18:39:08 2014
From: cpcloud at gmail.com (Phillip Cloud)
Date: Fri, 3 Jan 2014 12:39:08 -0500
Subject: [Pandas-dev] joris
In-Reply-To: <856D71AF-D25A-4AF5-A31D-544449122D0E@gmail.com>
References: <CAJPUwMCgEwfkST_u4dUpBNB5da=W+oaZAO62_y0r18bmi8tK6A@mail.gmail.com>
 <856D71AF-D25A-4AF5-A31D-544449122D0E@gmail.com>
Message-ID: <CAKRVfm67tvEtVMv+bTusaqve8QsyWmx2+WP8NS1+ZZYXVThEYg@mail.gmail.com>

Nice to have you on board!

On Friday, January 3, 2014, Jeff Reback wrote:

> joris
>
> shortly you should have ability to push to master!
>
> I think that you have been putting up quality PRs and very nicely
> commenting in others
>
> welcome to the team
>
> you might need to subscribe to pandas-dev ml (not sure how that gets added)
>
> Jeff
>
> Begin forwarded message:
>
> *From:* Wes McKinney <wesmckinn at gmail.com <javascript:_e({}, 'cvml',
> 'wesmckinn at gmail.com');>>
> *Date:* January 3, 2014 at 11:45:51 AM EST
> *To:* Jeff Reback <jeffreback at gmail.com <javascript:_e({}, 'cvml',
> 'jeffreback at gmail.com');>>
> *Cc:* "pandas-dev at python.org <javascript:_e({}, 'cvml',
> 'pandas-dev at python.org');>" <pandas-dev at python.org <javascript:_e({},
> 'cvml', 'pandas-dev at python.org');>>
> *Subject:* *Re: [Pandas-dev] joris*
>
> Consider it so. Happy new year everyone
>
> On Fri, Jan 3, 2014 at 8:21 AM, Jeff Reback <jeffreback at gmail.com<javascript:_e({}, 'cvml', 'jeffreback at gmail.com');>>
> wrote:
>
>
> I think jorisvandenbossche
>
> would be nice to add ability to push to master
>
>
> has done tremendous work with docs (and other PRs)
>
>
> Jeff
>
>
> _______________________________________________
>
> Pandas-dev mailing list
>
> Pandas-dev at python.org <javascript:_e({}, 'cvml',
> 'Pandas-dev at python.org');>
>
> https://mail.python.org/mailman/listinfo/pandas-dev
>
>

-- 

--
Best,
Phillip Cloud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140103/24e0639c/attachment-0001.html>

From jorisvandenbossche at gmail.com  Sat Jan  4 01:39:29 2014
From: jorisvandenbossche at gmail.com (Joris Van den Bossche)
Date: Sat, 4 Jan 2014 01:39:29 +0100
Subject: [Pandas-dev] joris
In-Reply-To: <CAKRVfm67tvEtVMv+bTusaqve8QsyWmx2+WP8NS1+ZZYXVThEYg@mail.gmail.com>
References: <CAJPUwMCgEwfkST_u4dUpBNB5da=W+oaZAO62_y0r18bmi8tK6A@mail.gmail.com>
 <856D71AF-D25A-4AF5-A31D-544449122D0E@gmail.com>
 <CAKRVfm67tvEtVMv+bTusaqve8QsyWmx2+WP8NS1+ZZYXVThEYg@mail.gmail.com>
Message-ID: <CALQtMBZvK0Mg6usZtcRzL4MuwSC+zgiFUc6YqpEQ50qun-Z9iA@mail.gmail.com>

Thanks all for your confidence, and Jeff for the nice words!
It is pleasant to feel that you can be of value, that your contributions
and feedback are appreciated.
Maybe less good news for my PhD ... :-), but yeah, that's life!

I was already subscribed to the mailing list, so that's OK.

Joris



2014/1/3 Phillip Cloud <cpcloud at gmail.com>

> Nice to have you on board!
>
>
> On Friday, January 3, 2014, Jeff Reback wrote:
>
>> joris
>>
>> shortly you should have ability to push to master!
>>
>> I think that you have been putting up quality PRs and very nicely
>> commenting in others
>>
>> welcome to the team
>>
>> you might need to subscribe to pandas-dev ml (not sure how that gets
>> added)
>>
>> Jeff
>>
>> Begin forwarded message:
>>
>> *From:* Wes McKinney <wesmckinn at gmail.com>
>> *Date:* January 3, 2014 at 11:45:51 AM EST
>> *To:* Jeff Reback <jeffreback at gmail.com>
>> *Cc:* "pandas-dev at python.org" <pandas-dev at python.org>
>> *Subject:* *Re: [Pandas-dev] joris*
>>
>> Consider it so. Happy new year everyone
>>
>> On Fri, Jan 3, 2014 at 8:21 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>>
>>
>> I think jorisvandenbossche
>>
>> would be nice to add ability to push to master
>>
>>
>> has done tremendous work with docs (and other PRs)
>>
>>
>> Jeff
>>
>>
>> _______________________________________________
>>
>> Pandas-dev mailing list
>>
>> Pandas-dev at python.org
>>
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>>
>
> --
>
> --
> Best,
> Phillip Cloud
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140104/d71bc8a3/attachment.html>

From wesmckinn at gmail.com  Tue Jan  7 01:58:12 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Mon, 6 Jan 2014 16:58:12 -0800
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <52C4D62D.5050303@gmx.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
Message-ID: <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>

Totally worn out today. I'll get on uploading the binaries first thing tomorrow

On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
> 0.13.0 was Tagged yesterday.
>
> Ping me when the binaries are up and I'll send out the ANN
> to the ml.
>
> Y
>
> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>> hi YP,
>>
>> Please go ahead and tag the release. Either you or Jeff should
>> announce the release on the usual channels once the binaries make it
>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>> do it then.
>>
>> cheers and happy new year
>> Wes
>>

From jeffreback at gmail.com  Wed Jan  8 20:26:08 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Wed, 8 Jan 2014 14:26:08 -0500
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
 <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
Message-ID: <C5E8E3B7-E7F7-4F1A-9492-7A5118453B83@gmail.com>

gr8

doc building  seems to have stalled on dev as we
thanks!
Jeff

> On Jan 6, 2014, at 7:58 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
> 
> Totally worn out today. I'll get on uploading the binaries first thing tomorrow
> 
>> On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
>> 0.13.0 was Tagged yesterday.
>> 
>> Ping me when the binaries are up and I'll send out the ANN
>> to the ml.
>> 
>> Y
>> 
>>> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>>> hi YP,
>>> 
>>> Please go ahead and tag the release. Either you or Jeff should
>>> announce the release on the usual channels once the binaries make it
>>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>>> do it then.
>>> 
>>> cheers and happy new year
>>> Wes
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

From yoval at gmx.com  Mon Jan 13 08:40:14 2014
From: yoval at gmx.com (yoval p.)
Date: Mon, 13 Jan 2014 09:40:14 +0200
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
 <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
Message-ID: <52D3985E.8030901@gmx.com>

We're still in a dev holding pattern for binaries, I think
it makes sense to make further changes to our release process.

I'd like to tag a v0.13.1, upload the binaries off the "BadgerBox"
to github's new-ish releases feature and send out the ANN.

Having no pypi release is unfortunate but stalling development
is even worse IMO. There's already a noticeable slowdown in activity,
and PRs are laying around for months.

As someone lured by wes (you fiend, you) to care about pandas as a
developer and not just a user, forcing the issue on release schedule
is just me doing my bit as janitorial support for @jreback.

Wes, are you cool with that?
Anyone else think this is a bad move?

Yoval


On 01/07/2014 02:58 AM, Wes McKinney wrote:
> Totally worn out today. I'll get on uploading the binaries first thing tomorrow
> 
> On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
>> 0.13.0 was Tagged yesterday.
>>
>> Ping me when the binaries are up and I'll send out the ANN
>> to the ml.
>>
>> Y
>>
>> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>>> hi YP,
>>>
>>> Please go ahead and tag the release. Either you or Jeff should
>>> announce the release on the usual channels once the binaries make it
>>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>>> do it then.
>>>
>>> cheers and happy new year
>>> Wes
>>>
> 



From yoval at gmx.com  Mon Jan 13 08:54:59 2014
From: yoval at gmx.com (yoval p.)
Date: Mon, 13 Jan 2014 09:54:59 +0200
Subject: [Pandas-dev] Unable to continue maintaining pandas windows
 binary builds
In-Reply-To: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
References: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
Message-ID: <52D39BD3.7070704@gmx.com>

- I've setup a consolidated CI status page:
  http://scatterci.github.io/ScatterCI-Pandas

  to help us keep windows green without your involvement.

- We've agreed that jreback or me (me) will be doing the ANN.
- I suggested in another thread we treat pushing
  binaries directly to GH as sufficient for sending
  an ANN and moving to the next release cycle.

 You can then push the binaries to pypi at your convenience.

Does that cover it or are there other issues that need to be tackled?

Y

On 11/07/2013 11:57 PM, Wes McKinney wrote:
> Chang and I aren't able (and have not been for a long time) to provide
> the care and attention needed to maintain the pandas Windows binaries
> and also the documentation builds. I'd like to find an alternative
> solution soon. pandas can't be the only project with this problem. Any
> ideas?
> 
> - Wes
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
> 


From yoval at gmx.com  Mon Jan 13 08:45:02 2014
From: yoval at gmx.com (yoval p.)
Date: Mon, 13 Jan 2014 09:45:02 +0200
Subject: [Pandas-dev] pandas 0.13 timeline
In-Reply-To: <CADwh0WPh_=GV4xRAPF65LbRnU9N5Ay1o3toMGAmNO_1w-6L1yg@mail.gmail.com>
References: <CAJPUwMD+oyxKiX2TV5et7rxo9QFMz6kdZpM06QZm+PRc7ievTw@mail.gmail.com>
 <CADwh0WPh_=GV4xRAPF65LbRnU9N5Ay1o3toMGAmNO_1w-6L1yg@mail.gmail.com>
Message-ID: <52D3997E.4010703@gmx.com>

Just pushed a fix and verified that the problem is solved:

http://pandas.pydata.org/pandas-build/dev/

pandas-0.13.0-122-g1e5f94a.win32-py2.7.exe

mod. getting 0.13 binaries out to pypi, you can clear the
artifacts dir and things will go back to normal.

Y

On 11/22/2013 10:25 PM, Chang She wrote:
> Hey guys,
> 
> Does anyone know jenkins well? I'm trying to fix a problem where the
> windows binaries are getting built with the jenkins job name + number in
> the file name.
> I tracked it down to the fact that jenkins is for some reason creating
> local tags that matches the jenkins job name + build number. 
> So when setup is run, the version number is that tag name, which means
> the windows binaries are built with that name.
> 
> I have teamviewer setup on the windows box here so if anyone is willing
> to help that would be much appreciated! Or if anyone know what's wrong
> and can tell me what to do, that would also work.
> 
> Thanks!!!
> 
> Chang
> 
> 
> On Sun, Nov 3, 2013 at 4:45 PM, Wes McKinney <wesmckinn at gmail.com
> <mailto:wesmckinn at gmail.com>> wrote:
> 
>     hi all,
> 
>     sorry I haven't been much help last few months. PyData is next weekend
>     and I definitely plan to have a 0.13 RC cut by then. I'll try to get
>     to remaining PR reviews you asked me about and I'll tinker with the
>     windows build machine tomorrow and report any windows-specific
>     failures.
> 
>     - Wes
>     _______________________________________________
>     Pandas-dev mailing list
>     Pandas-dev at python.org <mailto:Pandas-dev at python.org>
>     https://mail.python.org/mailman/listinfo/pandas-dev
> 
> 
> 
> 
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
> 


From wesmckinn at gmail.com  Tue Jan 14 22:19:07 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Tue, 14 Jan 2014 13:19:07 -0800
Subject: [Pandas-dev] Unable to continue maintaining pandas windows
	binary builds
In-Reply-To: <52D39BD3.7070704@gmx.com>
References: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
 <52D39BD3.7070704@gmx.com>
Message-ID: <CAJPUwMD7goPQJ9RZrdcr9SEk5PqP0Fb-T0zYAZ-HCvsqAQQPSQ@mail.gmail.com>

This is fine. I am going to nudge the windows CI box here and get the
binaries built this afternoon-- I need to move the VM to my laptop
rather than a box in the corner; unfortunate that having SSDs has made
toting a 60gb vm less desirable.

On Sun, Jan 12, 2014 at 11:54 PM, yoval p. <yoval at gmx.com> wrote:
> - I've setup a consolidated CI status page:
>   http://scatterci.github.io/ScatterCI-Pandas
>
>   to help us keep windows green without your involvement.
>
> - We've agreed that jreback or me (me) will be doing the ANN.
> - I suggested in another thread we treat pushing
>   binaries directly to GH as sufficient for sending
>   an ANN and moving to the next release cycle.
>
>  You can then push the binaries to pypi at your convenience.
>
> Does that cover it or are there other issues that need to be tackled?
>
> Y
>
> On 11/07/2013 11:57 PM, Wes McKinney wrote:
>> Chang and I aren't able (and have not been for a long time) to provide
>> the care and attention needed to maintain the pandas Windows binaries
>> and also the documentation builds. I'd like to find an alternative
>> solution soon. pandas can't be the only project with this problem. Any
>> ideas?
>>
>> - Wes
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

From wesmckinn at gmail.com  Tue Jan 14 22:47:22 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Tue, 14 Jan 2014 13:47:22 -0800
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <52D3985E.8030901@gmx.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
 <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
 <52D3985E.8030901@gmx.com>
Message-ID: <CAJPUwMC777T6vU_ofV_Hmqnns8aw40_jG2T7VA=GDKg4YX-yOg@mail.gmail.com>

I'm working on getting the 0.13.0 binaries up now. I'll try to get the
jenkins up and running again to check that all is green on master; I
can do 0.13.1 shortly thereafter whenever you tag-- just let me know.

Sorry to be holding up the releases; 0.14 and beyond will need a better system

- Wes

On Sun, Jan 12, 2014 at 11:40 PM, yoval p. <yoval at gmx.com> wrote:
> We're still in a dev holding pattern for binaries, I think
> it makes sense to make further changes to our release process.
>
> I'd like to tag a v0.13.1, upload the binaries off the "BadgerBox"
> to github's new-ish releases feature and send out the ANN.
>
> Having no pypi release is unfortunate but stalling development
> is even worse IMO. There's already a noticeable slowdown in activity,
> and PRs are laying around for months.
>
> As someone lured by wes (you fiend, you) to care about pandas as a
> developer and not just a user, forcing the issue on release schedule
> is just me doing my bit as janitorial support for @jreback.
>
> Wes, are you cool with that?
> Anyone else think this is a bad move?
>
> Yoval
>
>
> On 01/07/2014 02:58 AM, Wes McKinney wrote:
>> Totally worn out today. I'll get on uploading the binaries first thing tomorrow
>>
>> On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
>>> 0.13.0 was Tagged yesterday.
>>>
>>> Ping me when the binaries are up and I'll send out the ANN
>>> to the ml.
>>>
>>> Y
>>>
>>> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>>>> hi YP,
>>>>
>>>> Please go ahead and tag the release. Either you or Jeff should
>>>> announce the release on the usual channels once the binaries make it
>>>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>>>> do it then.
>>>>
>>>> cheers and happy new year
>>>> Wes
>>>>
>>
>
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

From yoval at gmx.com  Tue Jan 14 22:59:36 2014
From: yoval at gmx.com (yoval p.)
Date: Tue, 14 Jan 2014 23:59:36 +0200
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <CAJPUwMC777T6vU_ofV_Hmqnns8aw40_jG2T7VA=GDKg4YX-yOg@mail.gmail.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
 <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
 <52D3985E.8030901@gmx.com>
 <CAJPUwMC777T6vU_ofV_Hmqnns8aw40_jG2T7VA=GDKg4YX-yOg@mail.gmail.com>
Message-ID: <52D5B348.9030100@gmx.com>

gohlke has 0.13.0 windows binaries up including 3.3 and 3.4.
We just need those up on pypi where people expect them before
we can send out the ANN.

Y


On 01/14/2014 11:47 PM, Wes McKinney wrote:
> I'm working on getting the 0.13.0 binaries up now. I'll try to get the
> jenkins up and running again to check that all is green on master; I
> can do 0.13.1 shortly thereafter whenever you tag-- just let me know.
> 
> Sorry to be holding up the releases; 0.14 and beyond will need a better system
> 
> - Wes
> 
> On Sun, Jan 12, 2014 at 11:40 PM, yoval p. <yoval at gmx.com> wrote:
>> We're still in a dev holding pattern for binaries, I think
>> it makes sense to make further changes to our release process.
>>
>> I'd like to tag a v0.13.1, upload the binaries off the "BadgerBox"
>> to github's new-ish releases feature and send out the ANN.
>>
>> Having no pypi release is unfortunate but stalling development
>> is even worse IMO. There's already a noticeable slowdown in activity,
>> and PRs are laying around for months.
>>
>> As someone lured by wes (you fiend, you) to care about pandas as a
>> developer and not just a user, forcing the issue on release schedule
>> is just me doing my bit as janitorial support for @jreback.
>>
>> Wes, are you cool with that?
>> Anyone else think this is a bad move?
>>
>> Yoval
>>
>>
>> On 01/07/2014 02:58 AM, Wes McKinney wrote:
>>> Totally worn out today. I'll get on uploading the binaries first thing tomorrow
>>>
>>> On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
>>>> 0.13.0 was Tagged yesterday.
>>>>
>>>> Ping me when the binaries are up and I'll send out the ANN
>>>> to the ml.
>>>>
>>>> Y
>>>>
>>>> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>>>>> hi YP,
>>>>>
>>>>> Please go ahead and tag the release. Either you or Jeff should
>>>>> announce the release on the usual channels once the binaries make it
>>>>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>>>>> do it then.
>>>>>
>>>>> cheers and happy new year
>>>>> Wes
>>>>>
>>>
>>
>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
> 


From jeffreback at gmail.com  Tue Jan 14 23:18:35 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Tue, 14 Jan 2014 17:18:35 -0500
Subject: [Pandas-dev] Heads-Up: 0.13 final
In-Reply-To: <52D5B348.9030100@gmx.com>
References: <52BDE655.8010907@gmx.com>
 <CAJPUwMAZFWKkaj3hqUwuVZZpS7ai7_w3nb5ncgEq0TXngMbWhw@mail.gmail.com>
 <52C4D62D.5050303@gmx.com>
 <CAJPUwMB96d_6CSzTmvzHTFt8vXeZXrG+pbsm7Kan1pJutkzsmA@mail.gmail.com>
 <52D3985E.8030901@gmx.com>
 <CAJPUwMC777T6vU_ofV_Hmqnns8aw40_jG2T7VA=GDKg4YX-yOg@mail.gmail.com>
 <52D5B348.9030100@gmx.com>
Message-ID: <AE332F23-171C-4F54-9153-9E54A29256DA@gmail.com>

and migrate docs on pydata.org 

I can be reached on my cell 917-971-6387

> On Jan 14, 2014, at 4:59 PM, "yoval p." <yoval at gmx.com> wrote:
> 
> gohlke has 0.13.0 windows binaries up including 3.3 and 3.4.
> We just need those up on pypi where people expect them before
> we can send out the ANN.
> 
> Y
> 
> 
>> On 01/14/2014 11:47 PM, Wes McKinney wrote:
>> I'm working on getting the 0.13.0 binaries up now. I'll try to get the
>> jenkins up and running again to check that all is green on master; I
>> can do 0.13.1 shortly thereafter whenever you tag-- just let me know.
>> 
>> Sorry to be holding up the releases; 0.14 and beyond will need a better system
>> 
>> - Wes
>> 
>>> On Sun, Jan 12, 2014 at 11:40 PM, yoval p. <yoval at gmx.com> wrote:
>>> We're still in a dev holding pattern for binaries, I think
>>> it makes sense to make further changes to our release process.
>>> 
>>> I'd like to tag a v0.13.1, upload the binaries off the "BadgerBox"
>>> to github's new-ish releases feature and send out the ANN.
>>> 
>>> Having no pypi release is unfortunate but stalling development
>>> is even worse IMO. There's already a noticeable slowdown in activity,
>>> and PRs are laying around for months.
>>> 
>>> As someone lured by wes (you fiend, you) to care about pandas as a
>>> developer and not just a user, forcing the issue on release schedule
>>> is just me doing my bit as janitorial support for @jreback.
>>> 
>>> Wes, are you cool with that?
>>> Anyone else think this is a bad move?
>>> 
>>> Yoval
>>> 
>>> 
>>>> On 01/07/2014 02:58 AM, Wes McKinney wrote:
>>>> Totally worn out today. I'll get on uploading the binaries first thing tomorrow
>>>> 
>>>>> On Wed, Jan 1, 2014 at 6:59 PM, yoval p. <yoval at gmx.com> wrote:
>>>>> 0.13.0 was Tagged yesterday.
>>>>> 
>>>>> Ping me when the binaries are up and I'll send out the ANN
>>>>> to the ml.
>>>>> 
>>>>> Y
>>>>> 
>>>>>> On 12/30/2013 06:49 PM, Wes McKinney wrote:
>>>>>> hi YP,
>>>>>> 
>>>>>> Please go ahead and tag the release. Either you or Jeff should
>>>>>> announce the release on the usual channels once the binaries make it
>>>>>> through the tubes to PyPI. We'll be back in the office on 1/3 and can
>>>>>> do it then.
>>>>>> 
>>>>>> cheers and happy new year
>>>>>> Wes
>>>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>> 
> 
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

From wesmckinn at gmail.com  Wed Jan 15 07:09:20 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Tue, 14 Jan 2014 22:09:20 -0800
Subject: [Pandas-dev] Unable to continue maintaining pandas windows
	binary builds
In-Reply-To: <CAJPUwMD7goPQJ9RZrdcr9SEk5PqP0Fb-T0zYAZ-HCvsqAQQPSQ@mail.gmail.com>
References: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
 <52D39BD3.7070704@gmx.com>
 <CAJPUwMD7goPQJ9RZrdcr9SEk5PqP0Fb-T0zYAZ-HCvsqAQQPSQ@mail.gmail.com>
Message-ID: <CAJPUwMA8WQ5xqv=+fJ6ACqm5=bbRA9j--y7oQxV5T8Z5Uu4xVg@mail.gmail.com>

Binaries are uploaded, I'll post gohlke's other binaries when I can.
I'm gonna post the source tarballs now

On Tue, Jan 14, 2014 at 1:19 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
> This is fine. I am going to nudge the windows CI box here and get the
> binaries built this afternoon-- I need to move the VM to my laptop
> rather than a box in the corner; unfortunate that having SSDs has made
> toting a 60gb vm less desirable.
>
> On Sun, Jan 12, 2014 at 11:54 PM, yoval p. <yoval at gmx.com> wrote:
>> - I've setup a consolidated CI status page:
>>   http://scatterci.github.io/ScatterCI-Pandas
>>
>>   to help us keep windows green without your involvement.
>>
>> - We've agreed that jreback or me (me) will be doing the ANN.
>> - I suggested in another thread we treat pushing
>>   binaries directly to GH as sufficient for sending
>>   an ANN and moving to the next release cycle.
>>
>>  You can then push the binaries to pypi at your convenience.
>>
>> Does that cover it or are there other issues that need to be tackled?
>>
>> Y
>>
>> On 11/07/2013 11:57 PM, Wes McKinney wrote:
>>> Chang and I aren't able (and have not been for a long time) to provide
>>> the care and attention needed to maintain the pandas Windows binaries
>>> and also the documentation builds. I'd like to find an alternative
>>> solution soon. pandas can't be the only project with this problem. Any
>>> ideas?
>>>
>>> - Wes
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>
>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev

From wesmckinn at gmail.com  Wed Jan 15 07:19:41 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Tue, 14 Jan 2014 22:19:41 -0800
Subject: [Pandas-dev] Unable to continue maintaining pandas windows
	binary builds
In-Reply-To: <CAJPUwMA8WQ5xqv=+fJ6ACqm5=bbRA9j--y7oQxV5T8Z5Uu4xVg@mail.gmail.com>
References: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
 <52D39BD3.7070704@gmx.com>
 <CAJPUwMD7goPQJ9RZrdcr9SEk5PqP0Fb-T0zYAZ-HCvsqAQQPSQ@mail.gmail.com>
 <CAJPUwMA8WQ5xqv=+fJ6ACqm5=bbRA9j--y7oQxV5T8Z5Uu4xVg@mail.gmail.com>
Message-ID: <CAJPUwMBv5sRFR9Ncz7onxsR23F=xV_1xd-FtsXuK5UqSuzYKCA@mail.gmail.com>

OK everything is posted. Announce away, I shall tweet and give much
accolades on the social medias in the morning =D

On Tue, Jan 14, 2014 at 10:09 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
> Binaries are uploaded, I'll post gohlke's other binaries when I can.
> I'm gonna post the source tarballs now
>
> On Tue, Jan 14, 2014 at 1:19 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
>> This is fine. I am going to nudge the windows CI box here and get the
>> binaries built this afternoon-- I need to move the VM to my laptop
>> rather than a box in the corner; unfortunate that having SSDs has made
>> toting a 60gb vm less desirable.
>>
>> On Sun, Jan 12, 2014 at 11:54 PM, yoval p. <yoval at gmx.com> wrote:
>>> - I've setup a consolidated CI status page:
>>>   http://scatterci.github.io/ScatterCI-Pandas
>>>
>>>   to help us keep windows green without your involvement.
>>>
>>> - We've agreed that jreback or me (me) will be doing the ANN.
>>> - I suggested in another thread we treat pushing
>>>   binaries directly to GH as sufficient for sending
>>>   an ANN and moving to the next release cycle.
>>>
>>>  You can then push the binaries to pypi at your convenience.
>>>
>>> Does that cover it or are there other issues that need to be tackled?
>>>
>>> Y
>>>
>>> On 11/07/2013 11:57 PM, Wes McKinney wrote:
>>>> Chang and I aren't able (and have not been for a long time) to provide
>>>> the care and attention needed to maintain the pandas Windows binaries
>>>> and also the documentation builds. I'd like to find an alternative
>>>> solution soon. pandas can't be the only project with this problem. Any
>>>> ideas?
>>>>
>>>> - Wes
>>>> _______________________________________________
>>>> Pandas-dev mailing list
>>>> Pandas-dev at python.org
>>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>>
>>>
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev

From yoval at gmx.com  Wed Jan 15 13:33:35 2014
From: yoval at gmx.com (yoval p.)
Date: Wed, 15 Jan 2014 14:33:35 +0200
Subject: [Pandas-dev] Unable to continue maintaining pandas windows
 binary builds
In-Reply-To: <CAJPUwMBv5sRFR9Ncz7onxsR23F=xV_1xd-FtsXuK5UqSuzYKCA@mail.gmail.com>
References: <CAJPUwMCfbTmJS+-F5yrqF5qD-LGwKoA6qQ5EtUrgBvRjStGn=g@mail.gmail.com>
 <52D39BD3.7070704@gmx.com>
 <CAJPUwMD7goPQJ9RZrdcr9SEk5PqP0Fb-T0zYAZ-HCvsqAQQPSQ@mail.gmail.com>
 <CAJPUwMA8WQ5xqv=+fJ6ACqm5=bbRA9j--y7oQxV5T8Z5Uu4xVg@mail.gmail.com>
 <CAJPUwMBv5sRFR9Ncz7onxsR23F=xV_1xd-FtsXuK5UqSuzYKCA@mail.gmail.com>
Message-ID: <52D6801F.7030408@gmx.com>

ANN is away, pending in google groups.

Y


On 01/15/2014 08:19 AM, Wes McKinney wrote:
> OK everything is posted. Announce away, I shall tweet and give much
> accolades on the social medias in the morning =D
> 
> On Tue, Jan 14, 2014 at 10:09 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
>> Binaries are uploaded, I'll post gohlke's other binaries when I can.
>> I'm gonna post the source tarballs now
>>
>> On Tue, Jan 14, 2014 at 1:19 PM, Wes McKinney <wesmckinn at gmail.com> wrote:
>>> This is fine. I am going to nudge the windows CI box here and get the
>>> binaries built this afternoon-- I need to move the VM to my laptop
>>> rather than a box in the corner; unfortunate that having SSDs has made
>>> toting a 60gb vm less desirable.
>>>
>>> On Sun, Jan 12, 2014 at 11:54 PM, yoval p. <yoval at gmx.com> wrote:
>>>> - I've setup a consolidated CI status page:
>>>>   http://scatterci.github.io/ScatterCI-Pandas
>>>>
>>>>   to help us keep windows green without your involvement.
>>>>
>>>> - We've agreed that jreback or me (me) will be doing the ANN.
>>>> - I suggested in another thread we treat pushing
>>>>   binaries directly to GH as sufficient for sending
>>>>   an ANN and moving to the next release cycle.
>>>>
>>>>  You can then push the binaries to pypi at your convenience.
>>>>
>>>> Does that cover it or are there other issues that need to be tackled?
>>>>
>>>> Y
>>>>
>>>> On 11/07/2013 11:57 PM, Wes McKinney wrote:
>>>>> Chang and I aren't able (and have not been for a long time) to provide
>>>>> the care and attention needed to maintain the pandas Windows binaries
>>>>> and also the documentation builds. I'd like to find an alternative
>>>>> solution soon. pandas can't be the only project with this problem. Any
>>>>> ideas?
>>>>>
>>>>> - Wes
>>>>> _______________________________________________
>>>>> Pandas-dev mailing list
>>>>> Pandas-dev at python.org
>>>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pandas-dev mailing list
>>>> Pandas-dev at python.org
>>>> https://mail.python.org/mailman/listinfo/pandas-dev
> 


From yoval at gmx.com  Thu Jan 16 12:11:08 2014
From: yoval at gmx.com (yoval p.)
Date: Thu, 16 Jan 2014 13:11:08 +0200
Subject: [Pandas-dev] Update for pypi 0.13.0 tarball
Message-ID: <52D7BE4C.8030101@gmx.com>

As reported and answered on ml, this has already been fixed master last
week. Since the fix affects setup.py only, i've updated the tarball on
GH releases.

Wes, if you could clobber the tarball on pypi with
https://github.com/pydata/pandas/releases/download/v0.13.0/pandas-0.13.0.tar.gz

We can spare users the trouble of looking up the issue.

Thanks,
Y

From wesmckinn at gmail.com  Fri Jan 17 00:10:39 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Thu, 16 Jan 2014 15:10:39 -0800
Subject: [Pandas-dev] Update for pypi 0.13.0 tarball
In-Reply-To: <52D7BE4C.8030101@gmx.com>
References: <52D7BE4C.8030101@gmx.com>
Message-ID: <CAJPUwMCUXiAYe=EwkwXQSktkcD72XnGPi50MT9T-npmT8LO_hg@mail.gmail.com>

On Thu, Jan 16, 2014 at 3:11 AM, yoval p. <yoval at gmx.com> wrote:
> As reported and answered on ml, this has already been fixed master last
> week. Since the fix affects setup.py only, i've updated the tarball on
> GH releases.
>
> Wes, if you could clobber the tarball on pypi with
> https://github.com/pydata/pandas/releases/download/v0.13.0/pandas-0.13.0.tar.gz
>
> We can spare users the trouble of looking up the issue.
>
> Thanks,
> Y
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev

Uploaded

From jeffreback at gmail.com  Thu Jan 23 16:23:58 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Thu, 23 Jan 2014 10:23:58 -0500
Subject: [Pandas-dev] 0.13.1
Message-ID: <B6744399-3FA5-4028-98CE-4A9C56320809@gmail.com>

can we try to get all currently marked 0.13.1 resolved as soon as possible
or pls move to 0.14 if not critical

thanks

Jeff

From yoval at gmx.com  Thu Jan 23 17:25:03 2014
From: yoval at gmx.com (yoval p.)
Date: Thu, 23 Jan 2014 18:25:03 +0200
Subject: [Pandas-dev] 0.13.1
In-Reply-To: <B6744399-3FA5-4028-98CE-4A9C56320809@gmail.com>
References: <B6744399-3FA5-4028-98CE-4A9C56320809@gmail.com>
Message-ID: <52E1425F.9030102@gmx.com>

We're on schedule to release 0.13.1 next week, two weeks
after the ANN. afaic we can tag 0.13.1 now if the queue
is cleared and all recent issues have been triaged and
bumped to 0.14.0.

I'll do my bit to help close the hot-potato doc tweaks PRs
in time for the release if it comes to that.

Y

On 01/23/2014 05:23 PM, Jeff Reback wrote:
> can we try to get all currently marked 0.13.1 resolved as soon as possible
> or pls move to 0.14 if not critical
> 
> thanks
> 
> Jeff
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
> 


From yoval at gmx.com  Sun Jan 26 14:14:16 2014
From: yoval at gmx.com (yoval p.)
Date: Sun, 26 Jan 2014 15:14:16 +0200
Subject: [Pandas-dev] Heads-up: Releasing 0.13.1
Message-ID: <52E50A28.1030508@gmx.com>

Hi all,

It's been 2 weeks since the ANN and we've gotten the usual
bug reports, perf regressions and un-intrusive enhancements
largely taken care of.

We've done what we can to make sure a reasonably stable release
is available, and now we can start working on the longer 3 month release
cycle towards 0.14, and begin merging PRs like it's
nobody's business.

If you have concerns or comments about tagging 0.13.1 shortly,
now's the time to speak up, here or preferbly in the heads-up issue
at https://github.com/pydata/pandas/issues/6103.

If no blocker is raised, we'll be tagging 0.13.1 within
a few days.


Y