Hi guys and happy holidays, Status on 0.13: - The bug queue is empty - Windows is green here - We're awaiting confirmation on final sparc fixes from @yarikoptic - The RC period has maxed it's potential IMO. Instead of an RC2 as we planned, I suggest we release the final and hold off on new code for a couple of weeks (an RC except by name). That'll get more users trying it out but still leaves us a window to release 0.13.1 if we must. After that we'll launch the new 3 month release cycle for 0.14. Some PRs are already waiting in the queue so as to get maximum testing over the period until 0.14. Hopefully over time more and more of the big changes will be ready to merge at the beginning of a new cycle rather then near it's end. Wes & chang, are you cool with jreback/me tagging 0.13 once everything is in place? The ANN and binaries can follow when you manage to spare the time. Hopefully, with me watching the windows CI and jreback squashing them bugs conan-style that shouldn't take up much time. - Y
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 On Fri, Dec 27, 2013 at 12:43 PM, yoval p. <yoval@gmx.com> wrote:
Hi guys and happy holidays,
Status on 0.13: - The bug queue is empty - Windows is green here - We're awaiting confirmation on final sparc fixes from @yarikoptic - The RC period has maxed it's potential IMO.
Instead of an RC2 as we planned, I suggest we release the final and hold off on new code for a couple of weeks (an RC except by name). That'll get more users trying it out but still leaves us a window to release 0.13.1 if we must.
After that we'll launch the new 3 month release cycle for 0.14. Some PRs are already waiting in the queue so as to get maximum testing over the period until 0.14. Hopefully over time more and more of the big changes will be ready to merge at the beginning of a new cycle rather then near it's end.
Wes & chang, are you cool with jreback/me tagging 0.13 once everything is in place? The ANN and binaries can follow when you manage to spare the time. Hopefully, with me watching the windows CI and jreback squashing them bugs conan-style that shouldn't take up much time.
- Y
_______________________________________________ Pandas-dev mailing list Pandas-dev@python.org https://mail.python.org/mailman/listinfo/pandas-dev
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
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@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
gr8 doc building seems to have stalled on dev as we thanks! Jeff
On Jan 6, 2014, at 7:58 PM, Wes McKinney <wesmckinn@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@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@python.org https://mail.python.org/mailman/listinfo/pandas-dev
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@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
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@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@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@python.org https://mail.python.org/mailman/listinfo/pandas-dev
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@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@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@python.org https://mail.python.org/mailman/listinfo/pandas-dev
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@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@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@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@python.org https://mail.python.org/mailman/listinfo/pandas-dev
_______________________________________________ Pandas-dev mailing list Pandas-dev@python.org https://mail.python.org/mailman/listinfo/pandas-dev
participants (3)
-
Jeff Reback -
Wes McKinney -
yoval p.