Ok. That's a reasonable rationale. Let's keep it as it is for now.
Thanks for all of the bug triaging you've been doing this weekend!
Looks like you've been drinking the right kind of coffee!
Mike
On 08/19/2012 05:43 PM, Phil Elson wrote:
I made the "1.2.x known bugs" milestone. I wanted a
I made the "1.2.x known bugs" milestone. I wanted a way of drawing
attention to them, without bundling them in the 1.2.x milestone. The main
motivation for this was because there is nobody currently working on them,
yet they are confirmed bugs which, unless we address them, will be known
bugs in th
On 08/19/2012 01:38 PM, Damon McDougall wrote:
> On Sun, Aug 19, 2012 at 12:58:53PM -0400, Michael Droettboom wrote:
>> There seems to be a new milestone "1.2.x known bugs". Is there a good
>> reason to have two milestones for 1.2? As we enter into the freeze
>> phase for 1.2, it would be easier
There has been a lot of great work triaging and fixing bugs lately. This
release is going to see more new features and bugfixes than we've seen
in matplotlib in a long time. Thanks to everyone!
Here's my plan for tomorrow's feature freeze:
Let's try to get a handle on the PRs we have for 1.2.
On Sun, Aug 19, 2012 at 12:58:53PM -0400, Michael Droettboom wrote:
> There seems to be a new milestone "1.2.x known bugs". Is there a good
> reason to have two milestones for 1.2? As we enter into the freeze
> phase for 1.2, it would be easier to just track a single milestone.
According to mp
There seems to be a new milestone "1.2.x known bugs". Is there a good
reason to have two milestones for 1.2? As we enter into the freeze
phase for 1.2, it would be easier to just track a single milestone.
Mike
--
Live
