[asterisk-dev] Weekly Asterisk Issue Tracker Update

[Mark Michelson]

Leif Madsen wrote:
> Introduction
> ------------
> 
> Welcome to the first weekly issue tracker update email. The purpose of this
> email is to bring attention to issues in Asterisk that the community could get
> involved with. Some of the things we've heard over the years is that those new
> to Asterisk don't know exactly where to get involved, especially new developers
> who are looking for an issue to work on, but are a bit inundated with Asterisk
> internals and not too sure where to start.
> 
> On a weekly (or bi-weekly) basis, I will be putting together a small list of
> issues on the Asterisk issue tracker (http://issues.asterisk.org) that I feel
> are issues that may be a good starting point for developers new to the project,
> or for people who are interested in just testing out some cool new features.
> 
> I will be breaking down the issues into 3 sections:
> 
>   * 'New' Issues
>      -- Issues in the 'New' state in the bug tracker are those that are potential
>         bugs that need to be resolved. The best way to do this is to reproduce
>         the issue, resolve the issue locally, and then provide a patch for the
>         reporter to test. If your patch resolves the issue, it will then be
>         reviewed by a senior developer for coding guideline issues, and other
>         issues that a junior developer may run into.
> 
>         This is a great way for a junior developer to help out the community
>         while getting feedback from more experienced Asterisk developers!
> 
>   * Issues 'Ready for 'Testing'
>     -- Issues in the 'Ready for Testing' state are those that have been gone
>        through the initial bug triage to determine that there is an issue, but
>        now the patch needs to be tested in order to determine if it resolves the
>        reported issue, and to verify it hasn't produced any other side effects.
> 
>        Issues in the 'Ready for Testing' state could be either bugs that are
>        being resolved, or new features that are looking for a wider testing
>        audience. However, this section will only deal with bugs, while the next
>        section will specifically list new features that are ready for testing.
> 
>   * New Features
>     -- This section will list several open issues that are new features to the
>        Asterisk code base. These are issues that need either initial, or, a wider
>        range of testing from the community in various situations, verification
>        that documentation is provided, and that it works as written.
> 
>        These are issues that could be tested by anyone interested in helping make
>        sure the future features of Asterisk are well tested prior to them being
>        merged to the primary code base.
> 
> Additionally, I will be providing updates on issues from the previous week to
> let you know what is happening with them, and whether they were resolved.
> 
> If you have any questions, comments, or have an idea about an issue that should
> be listed here, please feel free to contact me at lmadsen at digium.com.
> 
> Thanks!
> Leif Madsen.
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 'New' Issues
> ------------
> 
> * 0014928: sip unregister CLI command doesn't send register invite with expire=0
>             to remote client. (https://issues.asterisk.org/view.php?id=14928)
> 
> * 0014730: Fix runlevels in Debian rc files
>             (https://issues.asterisk.org/view.php?id=14730)
> 
> * 0015158: Message: "Unable to handle indication 3".
>             (https://issues.asterisk.org/view.php?id=15158)

Heh, looks like  I sniped this one before the message got sent out. Sorry about 
that one :)

Mark Michelson