[asterisk-dev] How much backporting of Doxygen updates should I do?

[Andrew Latham]

On Tue, Oct 30, 2012 at 4:37 PM, Matthew Jordan <mjordan at digium.com> wrote:
> On 10/30/2012 12:38 PM, Andrew Latham wrote:
>> On Tue, Oct 30, 2012 at 1:31 PM, Matthew Jordan <mjordan at digium.com> wrote:
>>> On 10/30/2012 10:56 AM, Andrew Latham wrote:
>>
>> I do follow what you are saying Matt.  I am actually poking at a
>> slightly different topic.  The Doxygen configuration, and code blocks
>> call on content that is no longer included ie: CODINGGUIDELINES.txt as
>> quick example.  I am only looking to do the following.
>>
>> 1. Fix markup errors.
>> 2. Remove reference or link to proper content
>> 3. Spelling and language issues
>>
>> So to paint a picture with an example.  If there is a "\ref CDR
>> Backends" that is a page that "\include CDR_BACKENDS.TXT" then that is
>> what I need to fix, via a link to the wiki or what ever docs are
>> correct.
>
> Thanks for the clarification.
>
> To answer your original question: I think this is certainly appropriate
> for trunk.  As it is arguably an improvement, it does not have to be in
> 1.8+, but I'm open to that as a possibility.  As for release branches
> prior to 1.8, I don't think those are candidates for inclusion.
>
> --
> Matthew Jordan
> Digium, Inc. | Engineering Manager
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: http://digium.com & http://asterisk.org

When I get most of this done in Trunk then I will look for
show-stoppers.  AKA loading of files that do not exist and work on
updating 11, 10 and 1.8 with the obvious, file not found type errors.
Then time pending I would like to fix some major Doxygen markup
errors.

BTW the community resource page I added was just for testing the docs
at asterisk.org.  This is how I verified that the asterisk.org docs
were using an external config.  I can remove it at some point.

-- 
~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~