[Asterisk-Users] BugTracker Information - REPOST

[Josh Roberson]

All,

    As a bug marshal, I have noticed quite a few bugs that seem to get 
overlooked/ignored due to the fact that they do not have the appropriate 
information in the bug information fields, or bugnotes.  I am, 
therefore, Reposting an old post from July 26th, 2003, to help clarify 
the use of the Bugtracker.  Sorry if you have read it before; this is 
just an attempt to re-familiarize everyone with the information that 
should be included in the posts, which should help speed things along.

Thank you for your time, and attention.
twisted

--------------------ORIGIONAL POST------------------------
From: Mark Spencer
Subject: [Asterisk-Users] Bug Tracker Official Launch
Date: Sat, 26 Jul 2003 13:48:14 -0500 (CDT)

ANNOUNCEMENT: Bug Tracker/Feature Request System

http://bugs.digium.com/

Digium has introduced a bug tracking and feature request system for
Asterisk developers and users.  Due to the increased traffic on the
mailing list, and an inadequate number of hours in the day to parse
it, it has been decided that a more meaningful method of tracking
bugs, features, and patches had to be implemented.

The Asterisk developers pledge to do their best update and keep the bug
tracking system up to date so long as the users choose to utilize it
adequately.  We would encourage people from this point forward to log
their bugs and features in this system.  Simply sending things to the list
is insufficient notification for bug repair and tracking.  Unless
submitted to the bug tracker, there are no guarantees that your bugs are
even read, much less worked on.  (No guarantees if they are in the bug
tracker that they will be repaired, either, but they will be read and
examined.)

If you're a developer looking for a project, the bug tracker represents a
good place to start looking.  When you send patches to implement features
and fix bugs, be sure to referenche what bugs they fix (or features they
implement).

BUGS:
   Before submitting a bug into the system, make sure you have the
following information to submit:

   - your CVS date ("show version")
   - your operating system and revision ("uname -a")
   - your hardware configuration, if relevant (all cards and their configs)
   - your VoIP environment (SIP phones? H.323?  MGCP?)
   - if a corefile has been produced, please have a backtrace
        "gdb /usr/sbin/asterisk /path/to/corefile.1234"
        then type "bt" and include the output
   - include copies of relevant configuration files
   - full console error messages
   - debug traces (asterisk -vvvvvgcd) if applicable
   - WITHOUT ENOUGH DATA, YOUR BUG REPORT WILL BE REJECTED OR IGNORED

   What is a bug?  A bug is something that causes unexpected adverse
effects, contrary to what the stated or understood meaning of the
program intended.  A bug can be non-adherence to an RFC specification
that causes conflict with other packages in a specific command set.
A bug is a typo or syntax error in code.  A bug can be an example in
the documentation that does the opposite of what was intended.

   What is not a bug?  Anything that adds functionality past what was
intended in the code is a feature, and should be requested as such.
Clarification of documentation or comments in code, extension of a
protocol to include additional functionality, or support for a
different model or card would all be "features".

FEATURES
    There are many features and requests that are made of the system.
Please be as clear as you can as to what the feature is that you
need, and why it should be given priority over other features
currently in the queue.  The developers will examine all feature
requests, and at their discretion some may be implemented.
    Of course, if you supply code to implement the feature, it will be
much more likely that it will be integrated into the codebase.  See
"license" section, below this text.

LICENSE
    Please be aware that the Asterisk project, while Open Source under
GPL, code and patches which are contributed for distribution with core
Asterisk have additional requirements beyond the GPL.  In order to prevent
even the slightest possibility that a lawsuit could be brought against
Digium (the primary sponsor, and holder of the copyright,) it is required
that ALL patches and feature submitters have signed a waiver on the code
that they submit.

    Before ANY patch is applied, you MUST sign and return either of the
following document by fax, snail mail. Email only is unacceptable for
legal reasons.

     http://www.digium.com/disclaimer.txt
     http://www.digium.com/disclaim.changes

Personally, I'd like to thank everyone who has participated in fixing bugs
and adding features.  It's largly thanks to the feedback and assistance
from the community that Asterisk has managed to become so powerful in such
a short amount of time.

Mark