-
19 Mar 2009 12:50 AM #11Sencha User
- Join Date
- Feb 2008
- Posts
- 12
- Vote Rating
- 0
Is it possible for one of the devs to give an official response? I know you chaps are busy with 3.0 and the conference, but it would be great to get just an, "OK we heard you"...
-
19 Mar 2009 10:06 AM #12Sencha - Architect Dev Team
- Join Date
- Mar 2007
- Posts
- 8,191
- Vote Rating
- 63
We use Trac.
Originally Posted by davenolan
I'm not going to get involved in the question of why we don't allow people to publicly submit issues in our bugtracker.Aaron Conran
@aconran
Sencha Architect Development Team
-
19 Mar 2009 10:16 AM #13Sencha - Community Support Team
- Join Date
- Nov 2008
- Location
- San Diego, Peoples' Republic of California
- Posts
- 2,040
- Vote Rating
- 7
I would suggest Trac, too.
-
20 Mar 2009 12:33 AM #14Ext User
- Join Date
- Dec 2007
- Posts
- 159
- Vote Rating
- 0
What about public read-only access? That way, when a forum bug report is accepted as a bug a link to the trac bug report could be posted and we could see when a fix makes it into SVN / a release there.
-
20 Mar 2009 3:16 PM #15Ext JS Premium Member
- Join Date
- Mar 2007
- Posts
- 1,377
- Vote Rating
- 1
We can create our own Trac bug tracker for Ext.
Hmm... maybe I can set that up this weekend. I was just going over some of our fixes for Ext bugs today.
We thought about using ExtJS's hosted CDN version at some point, but the problem is that besides bugs not getting fixed, bugs that do get fixed take a long time to make it out into the public version. It ends up being useless. But it's no big deal to have your own CDN, but no "communal" benefit from using a common copy. Oh well.
-
20 Mar 2009 3:24 PM #16Ext JS Premium Member
- Join Date
- Mar 2007
- Posts
- 1,377
- Vote Rating
- 1
One other thing -- Trac (which we use) and others have xml/rpc modules so you can access them remotely... Meaning that you can also create a completely separate, ExtJS based front end to it. Which would be a cool project (ExtJS Corp could sponsor a Google Summer of Code project for such a thing!).
-
24 Mar 2009 2:46 AM #17Sencha User
- Join Date
- Feb 2008
- Posts
- 12
- Vote Rating
- 0
Sorry, what do you mean by "hosted CDN" version? Originally Posted by stever
Even if fixes take a long time to reach the public version, is it not still worthwhile having a single place for all information about an issue - including, say, patches for currently available versions?
-
24 Mar 2009 2:47 AM #18Sencha User
- Join Date
- Feb 2008
- Posts
- 12
- Vote Rating
- 0
Is that because it's a closed issue for the Devs or that it's not your area of concern? Originally Posted by aconran
-
24 Mar 2009 5:55 AM #19Ext User
- Join Date
- Jul 2007
- Location
- Florida
- Posts
- 9,996
- Vote Rating
- 1
MJ
API Search || Ext 3: docs-demo-upgrade guide || User Extension Repository
Frequently Asked Questions: FAQs
Tutorial: Grid (php/mysql/json) , Application Design and Structure || Extensions: MetaGrid, MessageWindow
-
24 Mar 2009 6:09 AM #20Sencha Premium Member
- Join Date
- Jun 2007
- Location
- Ostrava, Czech Republic
- Posts
- 43
- Vote Rating
- 1
bugtracking
bugtracking
hi,
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
Reply With Quote
