Sponsored link
Serve your customers, not your servers, with VERIO Linux VPS. Full-access test-drive here.
| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Re: 2.6 and 3.0 project management
| From: | Christian Heimes <lists-AT-cheimes.de> | |
| To: | python-dev-AT-python.org | |
| Subject: | Re: 2.6 and 3.0 project management | |
| Date: | Sun, 16 Mar 2008 19:23:09 +0100 | |
| Message-ID: | <frjoii$1oc$1@ger.gmane.org> | |
| Cc: | python-3000-AT-python.org | |
| Archive-link: | Article, Thread |
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 Python's way, I'm not going to stand in > it. Despite the url bugs.python.org it's an issue tracker and not a bug tracker. We track patches, feature requests, ideas and bugs in the same tracker. Christian _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-...
(Log in to post comments)