17 Mar 2009 6:38 AM #1
ExtJS needs a bugtracker
ExtJS needs a bugtracker
ExtJS needs a public read/write bugtracker. I know this has been raised several times before. Here are some reasons for not having a bugtracker I've seen on previous threads.
Bogus reason 1) We need the forum to screen out all the crud before it gets in the bugtracker.
This is not a good reason. People are already screening out the crud in the forum, right, in order to decide what goes in the private bugtracker? So why not do that task in, well, a bugtracker?
Bogus reason 2) Keeping the forum means there's a single search context for support, which is better for searchability
Overall, it's harder to search the forum than it is to search a bugtracker. In a bugtracker, issues are structured data. There are different ways to search, filter, sort, find, categorize etc. This is not the case with the forum, despite trying to enforce a consistent naming scheme.
The aim of having a single support area for everything can be acheived by either porting the forum to the bugtracker (lots of them have forums) (I will help). Or it can be abandoned - many other projects -larger projects, even - manage perfectly well having separate areas for help and for bugs/feature requests.
Bogus reason 3) There's just too many bugs filed that are just simple programming errors for a public bugtracker to work. There aren't the resouces to maintain it.
It's also much easier to keep track of just the issues you are interested in, both as a consumer and a dev. Every decent bugtracker will have a way of filtering out irrelevant or badly-formed issues.
Anyway, here's the conversation that prompted me to post this...
Me: I'd like to use ExtJS for the Dollortron 9000 project.
Boss: Kewl. <Googles> Where's the bugtracker? I can only find this ugly Vbulletin forum.
Me: Er, that's it apart from a private one the devs apparently use.
Boss: WTF? Are they serious? <Puts bulging wallet back in safe>
Boss may be right, boss may be wrong, but we dearly need a bugtracker.
Big love to all the devs and everyone who helps here. I just want to make everyone's life easier!
17 Mar 2009 7:07 AM #2
- Join Date
- Mar 2007
- Notts/Redwood City
- Vote Rating
A beautiful, Extified bugtracker, crafted by Mr Slocum himself.
It would enhance the product mightily, and probably be saleable because all other bugtrackers I have used are a little uncomfortable and fiddly to use.Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
17 Mar 2009 7:16 AM #3
17 Mar 2009 7:40 AM #4
+1 and also a trac timeline or equivalent would be really great !
17 Mar 2009 8:05 AM #5
+1. We make use of Jira in our company and love it. I know it's not open source, but it's the best we found. Nice and extensible too with a good API.
But whatever system you use, it's gotta be light years ahead of a forum .
17 Mar 2009 10:15 AM #6
agreed - we also use Jira - it's not perfect, but it works and it's easy to admin. i can't imagine using a forum for my bug tracking.
24 Mar 2009 6:09 AM #7
maybe reinventing wheel isn´t best way. try to look on jira from atlassian http://www.atlassian.com/software/jira/ they have also other sw and together is it quite complex solution.
even zend at leat on zend framework project choose it as issue tracking http://framework.zend.com/issues/sec...Navigator.jspa
pure web 2.0 tracker with ale extjs bells and whistles could be nice and also presented as complex demo application but imho time to write it should be used to move ext to next milestones
24 Mar 2009 11:49 AM #8
JIRA and TRAC both have remote capabilities which is how Eclipse is able to interoperate with both directly. So by that same token, you could create a ExtJS frontend for either.
However, Trac is free, JIRA is not. And there might be confusion with their open source exception, so it is best to just avoid it and any hastles that might come from that.
As for the idea of having workarounds -- I like that. Perhaps if we have our own bug database, we can restrict bug reports to only those that have workarounds. Not being in the Core group of ExtJS, I don't see much of a point of handling one otherwise.
Thread Participants: 24
- Animal (1 Post)
- harley.333 (1 Post)
- email@example.com (1 Post)
- aconran (1 Post)
- stever (3 Posts)
- ostghost (1 Post)
- mjlecomte (2 Posts)
- joeri (1 Post)
- durlabh (1 Post)
- jburnhams (2 Posts)
- mitchellsimoens (1 Post)
- mathieuj (1 Post)
- Kango_V (1 Post)
- mschwartz (1 Post)
- dougbieber (3 Posts)
- ssamayoa (4 Posts)
- shepsii (1 Post)
- brian428 (4 Posts)
- andrewx (1 Post)
- Bloodyaugust (2 Posts)
- jptrainor (2 Posts)
- dwils (3 Posts)
- walkout_ (1 Post)
- Event venue Singapore (1 Post)