asterisk

Commit Graph

Author	SHA1	Message	Date
Leif Madsen	7caa2349af	Merged revisions 328209 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.8 ........ r328209 \| lmadsen \| 2011-07-14 16:13:06 -0400 (Thu, 14 Jul 2011) \| 6 lines Introduce <support_level> tags in MODULEINFO. This change introduces MODULEINFO into many modules in Asterisk in order to show the community support level for those modules. This is used by changes committed to menuselect by Russell Bryant recently (r917 in menuselect). More information about the support level types and what they mean is available on the wiki at https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.10@328247 65c4cc65-6c06-0410-ace0-fbb531ad65f3	14 years ago
Tilghman Lesher	642bec4d6f	AST-2009-005 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@211539 65c4cc65-6c06-0410-ace0-fbb531ad65f3	16 years ago
Russell Bryant	c511a26749	Move Asterisk-addons modules into the main Asterisk source tree. Someone asked yesterday, "is there a good reason why we can't just put these modules in Asterisk?". After a brief discussion, as long as the modules are clearly set aside in their own directory and not enabled by default, it is perfectly fine. For more information about why a module goes in addons, see README-addons.txt. chan_ooh323 does not currently compile as it is behind some trunk API updates. However, it will not build by default, so it should be okay for now. git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3	16 years ago

Author

SHA1

Message

Date

Leif Madsen

7caa2349af

Merged revisions 328209 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r328209 | lmadsen | 2011-07-14 16:13:06 -0400 (Thu, 14 Jul 2011) | 6 lines
  
  Introduce <support_level> tags in MODULEINFO.
  This change introduces MODULEINFO into many modules in Asterisk in order to show
  the community support level for those modules. This is used by changes committed
  to menuselect by Russell Bryant recently (r917 in menuselect). More information about
  the support level types and what they mean is available on the wiki at
  https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
........


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.10@328247 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Tilghman Lesher

642bec4d6f

AST-2009-005

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@211539 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Russell Bryant

c511a26749

Move Asterisk-addons modules into the main Asterisk source tree.

Someone asked yesterday, "is there a good reason why we can't just put these
modules in Asterisk?".  After a brief discussion, as long as the modules are
clearly set aside in their own directory and not enabled by default, it is
perfectly fine.

For more information about why a module goes in addons, see README-addons.txt.

chan_ooh323 does not currently compile as it is behind some trunk API updates.
However, it will not build by default, so it should be okay for now.


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3

3 Commits (411fc37ea72b49411fecf1b7663bca7cfab84aa3)