On Tue, Mar 18, 2008 at 10:51 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> The key goal here (well, mine in any case :-)
> is to manage developers, not to get releases out at all cost. Even
> though the release schedule is set in stone, I think we should send
> out a variety of reminders a
On Tue, Mar 18, 2008 at 8:39 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Mar 18, 2008, at 12:11 AM, Guido van Rossum wrote:
> > Hm... This feels a bit like inflation of priorities to me; there would
> > be lots of critical bugs and quite a few release blockers... The
> > highest priority ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2008, at 12:11 AM, Guido van Rossum wrote:
> Hm... This feels a bit like inflation of priorities to me; there would
> be lots of critical bugs and quite a few release blockers... The
> highest priority just pertains to the upcoming release
Guido van Rossum wrote:
On Mon, Mar 17, 2008 at 11:49 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
We should not release the finals until there are no release blockers
or criticals. Either the critical gets moved to high and ignored, or
it gets moved to release blocker and gets fixed.
Hm...
On Mon, Mar 17, 2008 at 11:49 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Mar 17, 2008, at 11:35 PM, Guido van Rossum wrote:
>
> > What do I do for something that should absolutely go into the 2.6final
> > release (say) but is otherwise pretty minor? I've been using critical
> > to make s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 17, 2008, at 11:35 PM, Guido van Rossum wrote:
> What do I do for something that should absolutely go into the 2.6final
> release (say) but is otherwise pretty minor? I've been using critical
> to make sure it doesn't get put off until past the
What do I do for something that should absolutely go into the 2.6final
release (say) but is otherwise pretty minor? I've been using critical
to make sure it doesn't get put off until past the release.
On Mon, Mar 17, 2008 at 11:31 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 17, 2008
On Mon, Mar 17, 2008 at 9:10 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Barry, Neal, and myself had a conversation and changed the priority
> fields in the tracker. You can click on 'priority' to see an
> explanation, but the new fields are:
>
> - release blocker
> - critical
> - high
> -
Barry, Neal, and myself had a conversation and changed the priority
fields in the tracker. You can click on 'priority' to see an
explanation, but the new fields are:
- release blocker
- critical
- high
- normal
- low
So "release blocker" blocks a release. "Critical" could very easily
block a rele
