| Anonymous | Login | Signup for a new account | 2008-11-21 21:13 CST |
| Main | My View | View Issues | View Contributor License | Docs |
| Please read the guidelines! - 2005-02-13 20:02 - twisted [Announcement] |
| Just a reminder: Before you post a bug, please take the time to read the guidelines. There is a link on the Report Bug screen, as well as below (for your convenience). This will not only help you provide an efficient bug report, but allow your bug to be handled quickly and efficiently. http://asterisk.org/developers/bug-guidelines [^] Thank you! |
| Mantis Changes - 2007-06-29 14:46 - qwell |
| 1) Mantis Updated This is now using the most up to date version of Mantis. Also, all of our previous custom modifications have been ported to this version, including the karma system and code review fields for uploads. Furthermore, there have been some problems showing updates to karma values which should now be fixed. 2) Categorization Changes The existing categorization on bugs.digium.com is not very organized. It has now been completely redone. Asterisk now exists in a single project, instead of spread across multiple different ones. Within the Asterisk project, we have categories that look kind of like a directory structure. For example: Applications/app_dial CDR/cdr_odbc Channels/chan_sip/CodecHandling Channels/chan_sip/Subscriptions Previously, SIP was an entire project. That let you have multiple categories for SIP bugs, but also allow you to view all of them at once. To maintain this type of functionality, some wildcard functionality has been added to the category filtering. For example, to see all bugs related to chan_sip, you can set your Category filter to: Channels/chan_sip/* Also, all issues reported in the past have been mapped into the new project and category structure. 3) Subversion Integration It has long been common practice to include the related issue numbers in commit messages. Now, this does something! When you put "#1234", "issue 1234", or "bug 1234", the commit is automatically noted as a comment in the issue in Mantis. Furthermore, if you put "closes issue 1234", the commit will be noted in the bug, and it will also be automatically closed out. 4) ViewVC Integration When Mantis automatically references a commit in an issue, it will provide a link back to ViewVC to view the changeset to see what code changed. ViewVC has been modified to automatically link to Mantis when issue numbers are placed in commit messages. 5) Commit Message Templates You can now also have Mantis create a commit message template for you. It provides a set of check boxes so that you can decide which information to include. You can copy it in to your editor and add whatever additional information is needed to explain the changes being made, without having to go through putting in the issue number, who reported it, who provided patches, who provided testing, etc. 6) License Agreement (Disclaimer) Handling The bug tracker is now integrated with a database of contributor license agreements. This will make us much more accountable in the process of accepting submissions as the license agreement status should always be very clear. When a user is logged in, there is a link along the top for signing a license agreement. It can now be done on the web site, and does not have to be mailed or faxed to Digium. When uploading code or documentation submissions, the user will have to check a box to say that it is a submission. If they do not have a license agreement, it will be denied. Once the license is agreed to, uploads of contributions is allowed. The license has to be accepted by someone in the legal department at Digium before the uploads can be viewed by anyone but the owner of the file and administrators. Of course, a user could upload code without marking it as a code submission. It will have to become policy that as soon as a bug marshal sees that this has been done, the attachment is immediately deleted and the user is asked to upload it again, properly marking it as a submission. |
| New Fields in Bug Reports - 2004-10-11 23:03 - twisted |
| Hello Everyone! Since it's going to be increasingly difficult to determine the actual version of Asterisk you are using to report bugs, add patches and applications, and other tidbits too, I have added new fields: Version SVN Branch SVN Revision (number only) Disclaimer on file. Which should be filled out when you file a bug. If you are using SVN, *PLEASE* fill out the Branch and Revision fields. If you're using branch 1.2 for example, you would put 'SVN' in the Version field, '1.2' in the SVN Branch field, and the revision number (from 'show version') in the SVN Revision field. Thank you for your attention, and your contributions to making Asterisk a world-class telephony application! |
| Karma Karma Community - 2004-09-14 17:35 - malcolmd |
| With a page out of other online communities, the Asterisk Bug Tracker now features Karma. Those of you out there dying to raise or lower your Karma now have the option, based upon the bug reports and fixes you make. A big thanks to paulc for this one, we think it's great. http://bugs.digium.com/karma_halloffame.php [^] |
| Bug Tracker Documentation - 2004-01-08 15:08 - markster |
| Before submitting bugs, or if you are interested in becoming a bug marshal, please read the Bug Tracker Introduction: http://asterisk.org/developers/bug-guidelines [^] The current Bug Marshals, available on irc.freenode.net:6667, Freenode IRC, in the #asterisk-bugs channel are:
|
| Copyright © 2000 - 2008 Mantis Group |  |
bugs.digium.com runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA. | |
Please report problems with this site to asteriskteam@digium.com. |