Re: [matplotlib-devel] Fwd: v1.4 feature freeze + release timeline

2014-05-16 Thread Paul Ivanov
Thomas Kluyver, on 2014-05-16 08:56, wrote: > On 16 May 2014 01:17, "Eric Firing" wrote: > > Maybe this problem could be reduced by having a directory for CHANGELOG > > chunks, one file per PR, with the PR number as the filename. Then at > > release time they could be concatenated, edited, appen

[matplotlib-devel] Fwd: v1.4 feature freeze + release timeline

2014-05-16 Thread Thomas Kluyver
On 16 May 2014 01:17, "Eric Firing" wrote: > Maybe this problem could be reduced by having a directory for CHANGELOG > chunks, one file per PR, with the PR number as the filename. Then at > release time they could be concatenated, edited, appended to the real > CHANGELOG, and deleted. We already

Re: [matplotlib-devel] v1.4 feature freeze + release timeline

2014-05-16 Thread Till Stensitzki
Thanks for doing all this work, 1.4 is more than overdue! I justed wanted to chime in on Qt 5: Put it in and mark the support as experimental. So we can fix it in minor releases, also without exposure bugs won't be found. Till --

Re: [matplotlib-devel] v1.4 feature freeze + release timeline

2014-05-16 Thread Thomas Caswell
On Fri, May 16, 2014 at 4:17 AM, Eric Firing wrote: > Maybe this problem could be reduced by having a directory for CHANGELOG > chunks, one file per PR, with the PR number as the filename. Then at > release time they could be concatenated, edited, appended to the real > CHANGELOG, and deleted.

Re: [matplotlib-devel] v1.4 feature freeze + release timeline

2014-05-16 Thread Eric Firing
On 2014/05/15 5:16 PM, Thomas Caswell wrote: > Sorry for dropping the ball on moving things forward. On the contrary, you have been doing a great job on this, and you deserve a lot of thanks from all of us. > > I would propose a feature freeze this weekend and the goal of getting > the first RC