CC'd Etoys list.
I was waiting for someone to say this. If people aren't using mantis, could it be that mantis is ill-suited to the current process?
Maybe we don't need a bug database (I cringe, but it could be true.) Maybe we need a different tool, though.
How is Jira working out for the Etoys crowd?
FWIW, I think it's worth archiving mantis (if not just write-locking it somehow) if we did decide to put a bullet in it.
On Sep 6, 2010, at 9:26 PM, Andreas Raab andreas.raab@gmx.de wrote:
On 9/6/2010 8:32 PM, Sean P. DeNigris wrote:
Ken Causey wrote:
...Mantis is... purely optional and few Core Developers use it.
[shocked] Okay, problem solved. The "Bug Reporting" link on http://www.squeak.org/Community/ goes right to Mantis, so I always assumed that's how things were done. Maybe a more appropriate note would be on that page... something along the lines of "We currently use Mantis for issue tracking... got ya!" ;-)
The reality is that Mantis is completely overloaded with old crap. And we lack the man power to keep it current (if you're willing to help you're more than welcome). I think that what we should probably do is to just close all bugs older than two years to get a handle on it. Or perhaps close 'em all and start over. The real problem with bug trackers is that if they're not kept current all the time they tend to simply overflow.
My only outstanding question is: should I not bother entering things in Mantis and just upload to the inbox and be done with it? That would be simpler, obviously, but what's the most helpful?
At this point, the most effective approach is likely to just upload to the inbox. Since uploads are posted here we see them (we don't see bugs on Mantis that are posted, fixed, etc. - one of the major shortcomings). If the fix looks all right you've got a chance it'll be in. And if you provide a test, you got a *good* chance it'll go in.
Cheers,
- Andreas
On 07.09.2010, at 21:40, Casey Ransberger wrote:
CC'd Etoys list.
I was waiting for someone to say this. If people aren't using mantis, could it be that mantis is ill-suited to the current process?
Maybe we don't need a bug database (I cringe, but it could be true.) Maybe we need a different tool, though.
How is Jira working out for the Etoys crowd?
Not too well. It's not really suited to our needs. It seems geared toward tracking agile development with deadlines. But e.g. I can't set a ticket's status to "feedback needed" or "testing needed". Or add a cc to some other developer (a feature I liked about Trac). While it may be an excellent tool for some, I find most of its features useless to us.
If I could easily migrate all the tickets with their history to a new tracker I'd be a happy camper. It's not so simple unfortunately, and also a lot of URLs would break. Some redirect magic might solve this but it's all work nobody has time to spend on, so for now we're stuck with it.
- Bert -
FWIW, I think it's worth archiving mantis (if not just write-locking it somehow) if we did decide to put a bullet in it.
On Sep 6, 2010, at 9:26 PM, Andreas Raab andreas.raab@gmx.de wrote:
On 9/6/2010 8:32 PM, Sean P. DeNigris wrote:
Ken Causey wrote:
...Mantis is... purely optional and few Core Developers use it.
[shocked] Okay, problem solved. The "Bug Reporting" link on http://www.squeak.org/Community/ goes right to Mantis, so I always assumed that's how things were done. Maybe a more appropriate note would be on that page... something along the lines of "We currently use Mantis for issue tracking... got ya!" ;-)
The reality is that Mantis is completely overloaded with old crap. And we lack the man power to keep it current (if you're willing to help you're more than welcome). I think that what we should probably do is to just close all bugs older than two years to get a handle on it. Or perhaps close 'em all and start over. The real problem with bug trackers is that if they're not kept current all the time they tend to simply overflow.
My only outstanding question is: should I not bother entering things in Mantis and just upload to the inbox and be done with it? That would be simpler, obviously, but what's the most helpful?
At this point, the most effective approach is likely to just upload to the inbox. Since uploads are posted here we see them (we don't see bugs on Mantis that are posted, fixed, etc. - one of the major shortcomings). If the fix looks all right you've got a chance it'll be in. And if you provide a test, you got a *good* chance it'll go in.
Cheers,
- Andreas
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Casey Ransberger