Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Pierre GM
On May 31, 2011, at 9:06 PM, Ralf Gommers wrote: > > It is helpful to have this cleaned up, thanks Mark for taking the time for > this. Mind you, I do agree with y'all for the cleaning up. I just had a shock when I received the batch of what I thought were brand new bugs that turned up to have

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Ralf Gommers
On Tue, May 31, 2011 at 7:11 PM, Pauli Virtanen wrote: > Tue, 31 May 2011 11:44:15 -0500, Mark Wiebe wrote: > [clip] > >> I find very commendable to strive for consistency, mind you. I'm just > >> not not very comfortable with the idea of modifying old records a > >> posteriori to adjust to new p

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Pauli Virtanen
Tue, 31 May 2011 11:44:15 -0500, Mark Wiebe wrote: [clip] >> I find very commendable to strive for consistency, mind you. I'm just >> not not very comfortable with the idea of modifying old records a >> posteriori to adjust to new policies... > > I was under the impression this already was the pol

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Mark Wiebe
On Tue, May 31, 2011 at 11:14 AM, Pierre GM wrote: > > On May 31, 2011, at 6:06 PM, Bruce Southey wrote: > > > On 05/31/2011 10:33 AM, Mark Wiebe wrote: > >> On Tue, May 31, 2011 at 10:09 AM, Pierre GM > wrote: > >> > >> On May 31, 2011, at 4:25 PM, Mark Wiebe wrote: > >> > >> > It's so we can s

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Pierre GM
On May 31, 2011, at 6:06 PM, Bruce Southey wrote: > On 05/31/2011 10:33 AM, Mark Wiebe wrote: >> On Tue, May 31, 2011 at 10:09 AM, Pierre GM wrote: >> >> On May 31, 2011, at 4:25 PM, Mark Wiebe wrote: >> >> > It's so we can see what bugs are actually fixed for 2.0 (as opposed to a >> > prior

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Bruce Southey
On 05/31/2011 10:33 AM, Mark Wiebe wrote: On Tue, May 31, 2011 at 10:09 AM, Pierre GM > wrote: On May 31, 2011, at 4:25 PM, Mark Wiebe wrote: > It's so we can see what bugs are actually fixed for 2.0 (as opposed to a prior release), and a bug that's mar

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Mark Wiebe
On Tue, May 31, 2011 at 10:09 AM, Pierre GM wrote: > > On May 31, 2011, at 4:25 PM, Mark Wiebe wrote: > > > It's so we can see what bugs are actually fixed for 2.0 (as opposed to a > prior release), and a bug that's marked 'closed' but Unscheduled simply > doesn't make sense to me. > > I'm sorry,

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Pierre GM
On May 31, 2011, at 4:25 PM, Mark Wiebe wrote: > It's so we can see what bugs are actually fixed for 2.0 (as opposed to a > prior release), and a bug that's marked 'closed' but Unscheduled simply > doesn't make sense to me. I'm sorry, I'm still failing to see the logic. * You're not sure whet

Re: [Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Mark Wiebe
It's so we can see what bugs are actually fixed for 2.0 (as opposed to a prior release), and a bug that's marked 'closed' but Unscheduled simply doesn't make sense to me. -Mark On Tue, May 31, 2011 at 9:20 AM, Pierre GM wrote: > All, > Could somebody tell me the advantage of changing the milest

[Numpy-discussion] Changing milestones on tickets

2011-05-31 Thread Pierre GM
All, Could somebody tell me the advantage of changing the milestone of tickets that have been closed for more than 10 months ? I'm genuinely curious. P. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/