-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 22, 2008, at 11:31 AM, Martin v. Löwis wrote:
>> Thanks Martin, I think this will work for now. Is there any way
>> you can allow me to edit this query too?
>
> Not easily.
>
> I could just remove it, and allow you to create a new one (or you
> Thanks Martin, I think this will work for now. Is there any way you can
> allow me to edit this query too?
Not easily.
I could just remove it, and allow you to create a new one (or you create
one yourself, anyway, and I remove mine later).
Regards,
Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 17, 2008, at 12:27 AM, Martin v. Löwis wrote:
>> 'critical' is fine (or 'immediate'). My problem before was that I
>> couldn't do one query that gave me all the critical issues for
>> both 2.6 and 3.0. That certainly could have been pebk
> 'critical' is fine (or 'immediate'). My problem before was that I
> couldn't do one query that gave me all the critical issues for both
> 2.6 and 3.0. That certainly could have been pebkac though. Neal
> mentioned that that kind of query should be possible, if it's not
> already there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 3:56 PM, Guido van Rossum wrote:
> On Sun, Mar 16, 2008 at 12:24 PM, Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
>> I mentioned this to Guido and got a positive response, so let me
>> state
>> my preference for your feedback. I
On Sun, Mar 16, 2008 at 12:24 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> I mentioned this to Guido and got a positive response, so let me state
> my preference for your feedback. I plan on holding up the final
> releases until both versions are ready to go. I think this will help
> motivat
I don't see a lot of objections left against using the bug tracker. I
just talked to Neal and he's going to transfer all tasks from the 2.6
spreadsheet to the bug tracker.
I'll also be adding various other tasks., as I think of them.
We'll have to think about which keywords to use. We'll probably
Benjamin Peterson wrote:
> It's just depends on how you see the tracker. It's not just to "bug" tracker
> anymore, is it? On other projects I've worked with, we had separate areas
> for bugs, features, and tasks. (yes, it's SourceForge.) I found it easier to
> keep organized. However, if this is Py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 8:51 AM, Guido van Rossum wrote:
> However, looking at the calendar, I think we need to do a little more
> planning and management than we've typically done for Python releases.
> A final release in August means that we should plan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 8:51 AM, Guido van Rossum wrote:
> Python 3.0 and 2.6 are coming along really nice. I am optimistic that
> we can make the projected August date for the final releases of 2.6
> and 3.0. As you may remember, Barry (the new release m
On Sun, Mar 16, 2008 at 11:51 AM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> It's just depends on how you see the tracker. It's not just to "bug" tracker
> anymore, is it? On other projects I've worked with, we had separate areas
> for bugs, features, and tasks. (yes, it's SourceForge.) I found
On Sun, Mar 16, 2008 at 11:37 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 16, 2008 at 11:19 AM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
> > I don't like the idea of task like items in the main bug tracker.
>
> Why not? Bugs are also tasks, and need to be managed and triage
>> I don't like the idea of task like items in the main bug tracker.
Guido> Why not? Bugs are also tasks, and need to be managed and triaged
Guido> in the same way.
Agreed. Both bugs and tasks would be "issues" in Roundup parlance, along
with patches.
A further reason to keep this
On Sun, Mar 16, 2008 at 11:19 AM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> I don't like the idea of task like items in the main bug tracker.
Why not? Bugs are also tasks, and need to be managed and triaged in
the same way. It might be convenient to have everything in one
tracker. What's your
On Sun, Mar 16, 2008 at 8:51 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Python 3.0 and 2.6 are coming along really nice. I am optimistic that
> we can make the projected August date for the final releases of 2.6
> and 3.0. As you may remember, Barry (the new release manager for both)
> sugg
Guido van Rossum schrieb:
> But perhaps the best feature is "hot lists" -- arbitrary, ordered,
> groupings of selected bugs. Each bug can be assigned to as many hot
> lists as you want. Seeing the list of all bugs in a particular hot
> list is one click away. We use this for overlaying project man
Guido van Rossum wrote:
> In order to make such a tight release schedule we should try to come
> up with a list of tasks that need to be done, and prioritize them.
> This should include documentation, and supporting tools like 2to3. It
> should include features, backports of features, cleanup, bugs
Guido> It has a much more detailed set of categories, organized as a
Guido> tree. Our project alone probably has 20-30 different bug
Guido> categories. New bugs in those categories are automatically CC'ed
Guido> to our group's mailing list (which isn't the same as
Guido> auto-
On Sun, Mar 16, 2008 at 9:01 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> 2008/3/16, Guido van Rossum <[EMAIL PROTECTED]>:
> > they are a sufficient tool. In my day job at Google we've started to
> > do all task management for our project in the bug tracker (but that
> > tracker has some
2008/3/16, Guido van Rossum <[EMAIL PROTECTED]>:
> they are a sufficient tool. In my day job at Google we've started to
> do all task management for our project in the bug tracker (but that
> tracker has some features that make it particularly easy). Does anyone
Like which? Something that coul
Python 3.0 and 2.6 are coming along really nice. I am optimistic that
we can make the projected August date for the final releases of 2.6
and 3.0. As you may remember, Barry (the new release manager for both)
suggested that we synchronize releases of 2.6 and 3.0. Not only could
this potentially sav
21 matches
Mail list logo
