>>> Guido van Rossum wrote > A much better option appears to be RoundUp: > Ka-Ping Yee's winning entry in the Software Carpentry competition, > re-implemented by Richard Jones and Anthony Baxter, with four > co-developers, now in beta (release 0.4.1 at > http://sourceforge.net/projects/roundup). It's all Python, First bit - Richard's the roundup guy. I just do little helper bits. In pretty much every way, the above is giving me far too much credit. > (Of course, it must be usable for the end users > reporting bugs too. :-) What "usable" means here is possibly open to debate. Making the system as easy as possible to submit bugs means we get bugs like "From: Anonymous. Subject: python gives KeyError. Body: my homework gives a keyerror." > The point of this message is to start gathering requirements. Should this discussion continue on python-dev? > - A way to migrate the existing SF tracker contents. There are > references to 6-digit SF tracker IDs all over the Python source code > and CVS history, and it would be nice if these IDs were usable in > the new tracker. This should be doable. There's already an import facility. > - Features that simplify the tracking of how bugs and patches relate > to different release branches. This could ease the work for release > managers tremendously compared to the status quo. It should be > possible to indicate exactly which releases are affected by a bug, Doable. > and also in which releases it is (or will be) fixed. (Integration > with CVS would be nice but seems out of scope.) Integration with CVS in the sense of NeilS' message (look for magic keywords) would be possible with a variant on the standard mailgw code. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4