Two 1.2 milestones

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

According to mpl release calendar, the feature freeze is for 2.0, not
1.2.

Is this correct, or am I missing something?

···

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.

--
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

Thanks for pointing this out. There was some disagreement/discussion about what to call the next release. In the end, it was decided to call it 1.2.There was a 2.0 milestone for a while, and all of those were moved to 1.2. I'll update the calendar.

Mike

···

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 to just track a single milestone.

According to mpl release calendar, the feature freeze is for 2.0, not
1.2.

Is this correct, or am I missing something?

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 the release.

I don’t envisage the milestone to be a longterm thing, but I do think its helpful to separate them from things we definitely want to resolve before taking a 1.2.x cut. I would be happy even if we delete the milestone first thing after the freeze tomorrow.

Regards,

Phil

···

On 19 August 2012 18:54, Michael Droettboom <mdroe@…31…> wrote:

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 to just track a single milestone.

According to mpl release calendar, the feature freeze is for 2.0, not

1.2.

Is this correct, or am I missing something?

Thanks for pointing this out. There was some disagreement/discussion

about what to call the next release. In the end, it was decided to call

it 1.2.There was a 2.0 milestone for a while, and all of those were

moved to 1.2. I’ll update the calendar.

Mike


Live Security Virtual Conference

Exclusive live event will cover all the ways today’s security and

threat landscape has changed and how IT managers can respond. Discussions

will include endpoint security, mobile security and the latest in malware

threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 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 the release.

I don't envisage the milestone to be a longterm thing, but I do think its helpful to separate them from things we definitely want to resolve before taking a 1.2.x cut. I would be happy even if we delete the milestone first thing after the freeze tomorrow.

Regards,

Phil

On 19 August 2012 18:54, Michael Droettboom <mdroe@…31… > <mailto:mdroe@…31…>> wrote:

    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 to just track a single milestone.
    > According to mpl release calendar, the feature freeze is for
    2.0, not
    > 1.2.
    >
    > Is this correct, or am I missing something?
    >
    Thanks for pointing this out. There was some disagreement/discussion
    about what to call the next release. In the end, it was decided
    to call
    it 1.2.There was a 2.0 milestone for a while, and all of those were
    moved to 1.2. I'll update the calendar.

    Mike

    ------------------------------------------------------------------------------
    Live Security Virtual Conference
    Exclusive live event will cover all the ways today's security and
    threat landscape has changed and how IT managers can respond.
    Discussions
    will include endpoint security, mobile security and the latest in
    malware
    threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
    _______________________________________________
    Matplotlib-devel mailing list
    Matplotlib-devel@lists.sourceforge.net
    <mailto:Matplotlib-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/matplotlib-devel