Page 2 of 6 FirstFirst 1234 ... LastLast
Results 11 to 20 of 58

Thread: ExtJS needs a bugtracker

  1. #11
    Sencha User davenolan's Avatar
    Join Date
    Feb 2008
    Posts
    12
    Vote Rating
    37
      2  

    Default

    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"...

  2. #12
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    146
      -1  

    Default

    Quote Originally Posted by davenolan View Post
    Can one of the devs tell us what they use at the moment? It could be easier to start with that in the short term.
    We use Trac.

    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

  3. #13
    Sencha - Ext JS Dev Team mschwartz's Avatar
    Join Date
    Nov 2008
    Location
    San Diego, Peoples' Republic of California
    Posts
    2,061
    Vote Rating
    19
      2  

    Default

    I would suggest Trac, too.

  4. #14
    Ext User
    Join Date
    Dec 2007
    Posts
    159
    Vote Rating
    4
      2  

    Default

    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.

  5. #15
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,408
    Vote Rating
    9
      2  

    Default

    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.

  6. #16
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,408
    Vote Rating
    9
      2  

    Thumbs up

    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!).

  7. #17
    Sencha User davenolan's Avatar
    Join Date
    Feb 2008
    Posts
    12
    Vote Rating
    37
      2  

    Default

    Quote Originally Posted by stever View Post
    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.
    Sorry, what do you mean by "hosted CDN" version?

    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?

  8. #18
    Sencha User davenolan's Avatar
    Join Date
    Feb 2008
    Posts
    12
    Vote Rating
    37
      2  

    Default

    Quote Originally Posted by aconran View Post
    I'm not going to get involved in the question of why we don't allow people to publicly submit issues in our bugtracker.
    Is that because it's a closed issue for the Devs or that it's not your area of concern?

  9. #19
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    8
      2  

    Default

    Quote Originally Posted by davenolan View Post
    Sorry, what do you mean by "hosted CDN" version?
    http://extjs.com/blog/2008/11/18/ext...t-performance/

  10. #20
    Sencha Premium Member
    Join Date
    Jun 2007
    Location
    Ostrava, Czech Republic
    Posts
    43
    Vote Rating
    3
      2  

    Lightbulb bugtracking

    hi,

    maybe reinventing wheel isnt 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

Page 2 of 6 FirstFirst 1234 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •