<p>Corey Farrell has uploaded this change for <strong>review</strong>.</p><p><a href="https://gerrit.asterisk.org/7269">View Change</a></p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">doxygen: Remove obsolete contents.<br><br>Remove doxygen contents that have nothing to do with the current state<br>of Asterisk.<br><br>Change-Id: Ic072cc8641f9533a202990ccf275ce87e3efd95c<br>---<br>D include/asterisk/doxygen/asterisk-git-howto.h<br>D include/asterisk/doxygen/commits.h<br>D include/asterisk/doxygen/releases.h<br>D include/asterisk/doxygen/reviewboard.h<br>M include/asterisk/doxyref.h<br>5 files changed, 0 insertions(+), 774 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">git pull ssh://gerrit.asterisk.org:29418/asterisk refs/changes/69/7269/1</pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">diff --git a/include/asterisk/doxygen/asterisk-git-howto.h b/include/asterisk/doxygen/asterisk-git-howto.h<br>deleted file mode 100644<br>index 1ecce15..0000000<br>--- a/include/asterisk/doxygen/asterisk-git-howto.h<br>+++ /dev/null<br>@@ -1,235 +0,0 @@<br>-/*<br>- * Asterisk -- An open source telephony toolkit.<br>- *<br>- * Copyright (C) 1999 - 2009, Digium, Inc.<br>- *<br>- * See http://www.asterisk.org for more information about<br>- * the Asterisk project. Please do not directly contact<br>- * any of the maintainers of this project for assistance;<br>- * the project provides a web site, mailing lists and IRC<br>- * channels for your use.<br>- *<br>- * This program is free software, distributed under the terms of<br>- * the GNU General Public License Version 2. See the LICENSE file<br>- * at the top of the source tree.<br>- */<br>-<br>-/*!<br>- * \file<br>- */<br>-<br>-/*!<br>- * \page AsteriskGitHowto How to setup a local GIT mirror of the Asterisk SVN repository<br>- *<br>- * <hr><br>- *<br>- * \section Introduction Introduction<br>- * This document will instruct you how to setup a local git mirror of the <br>- * Asterisk SVN repository.<br>- * <br>- * Why would you want that? for starters, it's a fast repository browser<br>- * and works well even when offline. More on why and why not at 'Pros and Cons'<br>- * in the end of this document. <br>- * <hr><br>- *<br>- * \section Setup Setup<br>- *<br>- * Make sure you have the package<br>- *<br>- \verbatim<br>- git-svn<br>- \endverbatim<br>- *<br>- * installed. It is part of the standard git distribution and included in<br>- * any recent Linux distribution.<br>- *<br>- * Next, get the files from this repository: <br>- *<br>- \verbatim<br>- git clone http://git.tzafrir.org.il/git/asterisk-tools.git<br>- \endverbatim<br>- *<br>- * Which will create the subdirectory 'asterisk-tools' under your working <br>- * directory. For the purpose of this HOWTO I assume that you will later <br>- * download Asterisk under the same directory.<br>- * <br>- * Now let's get Asterisk:<br>- * <br>- \verbatim<br>- git svn clone -s http://svn.digium.com/svn/asterisk<br>- \endverbatim<br>- * <br>- * This will download the whole /trunk , /tags and /branches hirarchies<br>- * to a new git repository under asterisk/ .<br>- * This will take a L O N G time. In the order of magnitude of a<br>- * day. If it stops in the middle:<br>- *<br>- \verbatim<br>- # cd asterisk; git svn fetch --fetch-all<br>- \endverbatim<br>- *<br>- * All commands as of this point are run from the newly-created subdirectory<br>- * 'asterisk'<br>- *<br>- \verbatim<br>- cd asterisk<br>- \endverbatim<br>- *<br>- * Next make your repository more compact:<br>- * <br>- * \note FIXME: I now get a .git subdirectory of the size of 135MB. This seems<br>- * overly large considering what I got a few monthes ago.<br>- *<br>- \verbatim<br>- git repack -a<br>- \endverbatim<br>- *<br>- * Now fix the menuselect bits. One possible venue is to use submodules.<br>- * This would require setting a separate menuselect repository . And<br>- * fixing the submodule references in every new tag to point to the right<br>- * place. I gave up at this stage, and instead reimplememented menuselect<br>- *<br>- \verbatim<br>- cp -a ../asterisk-tools/menuselect menuselect<br>- make -C menuselect dummies<br>- chmod +x menuselect/menuselect<br>- \endverbatim<br>- * <br>- * Next thing to do is ignore generated files. .gitignore is somewhat<br>- * like svn:ignore . Though it is possible to use one at the top<br>- * directory. Hence I decided to make it ignore itself as well:<br>- *<br>- \verbatim<br>- cp ../asterisk-tools/asterisk_gitignore .gitignore<br>- \endverbatim<br>- * <br>- * Now let's generate tags that will point to the tags/* branches.<br>- * e.g. tag 'v1.4.8' will point to the head of branch tags/1.4.8 .<br>- * If you don't like the extra 'v', just edit the sed command.<br>- *<br>- \verbatim<br>- ../asterisk-tools/update_tags<br>- \endverbatim<br>- * <br>- * Example configuration (refer to menuselect/menuselelct for more<br>- * information). For instance: res_snmp breaks building 1.4 from git:<br>- *<br>- \verbatim<br>- echo 'exclude res_snmp' >build_tools/conf<br>- \endverbatim<br>- *<br>- * <hr><br>- *<br>- * \section Update Update<br>- * The main Asterisk repository tends to get new commits occasionally. I<br>- * suppose you want those updates in your local copy. The following command<br>- * should normally be done from the master branch. If you actually use branches, <br>- * it is recommended to switch to it beforehand:<br>- *<br>- \verbatim<br>- git checkout master<br>- \endverbatim<br>- *<br>- * Next, get all updates.<br>- * <hr><br>- *<br>- * \section Usage Usage<br>- *<br>- * If you use git from the command-line, it is highly recommended to enable<br>- * programmable bash completion. The git command-line is way more complex<br>- * than svn, but the completion makes it usable:<br>- *<br>- *<br>- \verbatim<br>- asterisk$ git show v1.2.28<tab><tab><br>- v1.2.28 v1.2.28.1<br>-<br>- asterisk$ git show v1.2.28:c<tab><tab><br>- callerid.c channel.c cli.c coef_out.h contrib/<br>- cdr/ channels/ codecs/ config.c cryptostub.c<br>- cdr.c chanvars.c coef_in.h configs/ cygwin/<br>-<br>- asterisk$ git svn<tab><tab><br>- clone fetch log set-tree<br>- commit-diff find-rev propget show-externals<br>- create-ignore info proplist show-ignore<br>- dcommit init rebase<br>-<br>- asterisk$ git svn rebase --f<br>- --fetch-all --follow-parent<br>- \endverbatim<br>- * <br>- * Some useful commands:<br>- *<br>- \verbatim<br>- git svn rebase --fetch-all # pull updates from upstream<br>- man git-FOO # documentation for 'git FOO'<br>- # <tree> is any place on graph of branches: HEAD, name of a branch or<br>- # a tag, commit ID, and some others<br>- git show <tree> # The top commit in this tree (log + diff)<br>- git show <tree>:directory # directory listing<br>- git show <tree>:some/file # get that file<br>- git log <tree> # commit log up to that point<br>- git branch # shows local branches and in which one you are<br>- git branch -r # List remote branches. Such are SVN ones.<br>- \endverbatim<br>- *<br>- * For more information, see the man page gittutorial as well as<br>- * \arg http://git-scm.com/documentation<br>- *<br>- \verbatim<br>- git svn rebase --fetch-all<br>- \endverbatim<br>- *<br>- * <hr><br>- *<br>- * \section ProsAndCons Pros and Cons<br>- *<br>- * \subsection TheGood The Good<br>- *<br>- * Working off-line:<br>- * If you want to be able to use 'svn log' and 'svn diff' to a different<br>- * branch, now you can.<br>- *<br>- * Efficient repository browser:<br>- * With git you can effectively browse commit logs and working copies of<br>- * various branches. In fact, using it merely as a logs and versions<br>- * browser can be useful on its own.<br>- *<br>- * Branches really work:<br>- * With SVN merging a branch is complicated. Partially because lack of<br>- * separate merge tracking.With git you don't need the extra svnmerge:<br>- * changes that don't collide with your branch merge in a quick merge<br>- * operation.<br>- *<br>- * \subsection Limitations Limitations<br>- * <br>- * svn:externals :<br>- * does not really work well with git-svn (and similar systems: svk,<br>- * bzr-svn and hg-svn). Git has something called submodules that allows<br>- * emulating the basic functionality of svn:externals, but is not as<br>- * transparent.<br>- *<br>- * Commiting:<br>- * Not sure how safe it is to commit from such a copy. In most places I<br>- * see that it is not recommended to commit directly from git-svn. OTOH,<br>- * git has some tools that make it easy to prepare a patch set out of a<br>- * branch (e.g. git format-patch).<br>- *<br>- * IIRC there are also some issues for git-svn with https certificate<br>- * authentication in the first place.<br>- *<br>- * Tags:<br>- * /tags are branches. SVN tags are really branches that we pretend not<br>- * to change. And in fact in Asterisk we practically do change. But see<br>- * workaround below to generate tags from the tag branches.<br>- *<br>- * /team branches::<br>- * At least with git 1.5.x you can't easily follow all the team branches.<br>- * This is due to a bug in their handling of wildcards in branches<br>- * description. I believe this has been resolved in 1.6 but I didn't get<br>- * to test that. Even if it will, it will require an extra step of manual<br>- * editing.<br>- *<br>- * <hr><br>- */<br>diff --git a/include/asterisk/doxygen/commits.h b/include/asterisk/doxygen/commits.h<br>deleted file mode 100644<br>index 032bfc5..0000000<br>--- a/include/asterisk/doxygen/commits.h<br>+++ /dev/null<br>@@ -1,114 +0,0 @@<br>-/*<br>- * Asterisk -- An open source telephony toolkit.<br>- *<br>- * Copyright (C) 1999 - 2009, Digium, Inc.<br>- *<br>- * See http://www.asterisk.org for more information about<br>- * the Asterisk project. Please do not directly contact<br>- * any of the maintainers of this project for assistance;<br>- * the project provides a web site, mailing lists and IRC<br>- * channels for your use.<br>- *<br>- * This program is free software, distributed under the terms of<br>- * the GNU General Public License Version 2. See the LICENSE file<br>- * at the top of the source tree.<br>- */<br>-<br>-/*!<br>- * \file<br>- */<br>-<br>-/*!<br>- * \page CommitMessages Guidelines for Commit Messages<br>- *<br>- * <hr><br>- *<br>- * \section CommitMsgFormatting Commit Message Formatting<br>- *<br>- * The following illustrates the basic outline for commit messages:<br>- *<br>- * \verbatim<br>- * <One-liner summary of changes><br>- *<br>- * <Empty Line> <br>- *<br>- * <Verbose description of the changes><br>- *<br>- * <Empty Line> <br>- *<br>- * <Special Tags><br>- * \endverbatim<br>- *<br>- * Some commit history viewers treat the first line of commit messages as the<br>- * summary for the commit. So, an effort should be made to format our commit<br>- * messages in that fashion. The verbose description may contain multiple <br>- * paragraphs, itemized lists, etc. Always end the first sentence (and any<br>- * subsequent sentences) with punctuation.<br>- *<br>- * Commit messages should be wrapped at 80 %columns.<br>- *<br>- * \note For trivial commits, such as "fix the build", or "fix spelling mistake",<br>- * the verbose description may not be necessary.<br>- *<br>- * <hr><br>- *<br>- * \section CommitMsgTags Special Tags for Commit Messages<br>- *<br>- * \subsection MantisTags Mantis (https://issues.asterisk.org/)<br>- *<br>- * To have a commit noted in an issue, use a tag of the form: <br>- * \arg (issue #1234)<br>- *<br>- * To have a commit automatically close an issue, use a tag of the form:<br>- * \arg (closes issue #1234)<br>- *<br>- * When making a commit for a mantis issue, it is easiest to use the<br>- * provided commit %message template functionality. It will format the<br>- * special tags appropriately, and will also include information about who<br>- * reported the issue, which patches are being applied, and who did testing.<br>- * <br>- * Assuming that you have bug marshal access (and if you have commit access,<br>- * it is pretty safe to assume that you do), you will find the commit %message<br>- * template section directly below the issue details section and above the<br>- * issue relationships section. You will have to click the '+' next to<br>- * "Commit message template" to make the contents of the section visible.<br>- *<br>- * Here is an example of what the template will generate for you:<br>- *<br>- * \verbatim<br>- * (closes issue #1234)<br>- * Reported by: SomeGuy<br>- * Patches:<br>- * fix_bug_1234.diff uploaded by SomeDeveloper (license 5678)<br>- * \endverbatim<br>- *<br>- * If the patch being committed was written by the person doing the commit,<br>- * and is not available to reference as an upload to the issue, there is no<br>- * need to include something like "fixed by me", as that will be the default<br>- * assumption when a specific patch is not referenced.<br>- *<br>- * \subsection ReviewBoardTags Review Board (https://reviewboard.asterisk.org/)<br>- *<br>- * To have a commit set a review request as submitted, include the full URL<br>- * to the review request. For example:<br>- * \arg Review: %https://reviewboard.asterisk.org/r/95/<br>- *<br>- * \note The trailing slash in the review URL is required.<br>- *<br>- * <hr><br>- *<br>- * \section CommitMsgSvnmerge Commit Messages with svnmerge<br>- *<br>- * When using the svnmerge tool for merging changes between branches, use the<br>- * commit %message generated by svnmerge. The '-f' option to svnmerge allows<br>- * you to specify a file for svnmerge to write out a commit %message to. The<br>- * '-F' option to svn commit allows you to specify a file that contains the<br>- * commit %message.<br>- *<br>- * If you are using the expect script wrappers for svnmerge from repotools,<br>- * a commit %message is automatically placed in the file '../merge.msg'.<br>- *<br>- * For more detailed information about working with branches and merging,<br>- * see the following page on %asterisk.org:<br>- * \arg https://wiki.asterisk.org/wiki/display/AST/Subversion+Usage<br>- */<br>diff --git a/include/asterisk/doxygen/releases.h b/include/asterisk/doxygen/releases.h<br>deleted file mode 100644<br>index d1b33ff..0000000<br>--- a/include/asterisk/doxygen/releases.h<br>+++ /dev/null<br>@@ -1,294 +0,0 @@<br>-/*<br>- * Asterisk -- An open source telephony toolkit.<br>- *<br>- * Copyright (C) 1999 - 2009, Digium, Inc.<br>- *<br>- * See http://www.asterisk.org for more information about<br>- * the Asterisk project. Please do not directly contact<br>- * any of the maintainers of this project for assistance;<br>- * the project provides a web site, mailing lists and IRC<br>- * channels for your use.<br>- *<br>- * This program is free software, distributed under the terms of<br>- * the GNU General Public License Version 2. See the LICENSE file<br>- * at the top of the source tree.<br>- */<br>-<br>-/*!<br>- * \file<br>- */<br>-<br>-/*!<br>- * \page ReleaseStatus Asterisk Release Status<br>- *<br>- * \section warranty Warranty<br>- * The following warranty applies to all open source releases of Asterisk:<br>- *<br>- * NO WARRANTY<br>- *<br>- * BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY<br>- * FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN<br>- * OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES<br>- * PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED<br>- * OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<br>- * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS<br>- * TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE<br>- * PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,<br>- * REPAIR OR CORRECTION.<br>-<br>- * IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING<br>- * WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR<br>- * REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,<br>- * INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING<br>- * OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED<br>- * TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY<br>- * YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER<br>- * PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE<br>- * POSSIBILITY OF SUCH DAMAGES.<br>- *<br>- * \section releasestatustypes Release Status Types<br>- *<br>- * Release management is a essentially an agreement between the development<br>- * community and the %user community on what kind of updates can be expected<br>- * for Asterisk releases, and what types of changes these updates will contain.<br>- * Once these policies are established, the development community works very<br>- * hard to adhere to them. However, the development community does reserve<br>- * the right to make exceptions to these rules for special cases as the need<br>- * arises.<br>- *<br>- * Asterisk releases are in various states of maintenance. The states are<br>- * defined here:<br>- *<br>- * \arg <b>None</b> - This release series is receiving no updates whatsoever.<br>- * \arg <b>Security-Only</b> - This release series is receiving updates, but<br>- * only to address security issues. Security issues found and fixed in<br>- * this release series will be accompanied by a published security advisory<br>- * from the Asterisk project.<br>- * \arg <b>Full-Support</b> - This release series is receiving updates for all<br>- * types of bugs.<br>- * \arg <b>Full-Development</b> - Changes in this part of Asterisk include bug<br>- * fixes, as well as new %features and architectural improvements.<br>- *<br>- * \section AsteriskReleases Asterisk Maintenance Levels<br>- *<br>- * \htmlonly<br>- * <table border="1"><br>- * <tr><br>- * <td><b>Name</b></td><br>- * <td><b>SVN Branch</b></td><br>- * <td><b>Status</b></td><br>- * <td><b>Notes</b></td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk 1.0</td><br>- * <td>/branches/1.0</td><br>- * <td>None</td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk 1.2</td><br>- * <td>/branches/1.2</td><br>- * <td>Security-Only</td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk 1.4</td><br>- * <td>/branches/1.4</td><br>- * <td>Full-Support</td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk 1.6.0</td><br>- * <td>/branches/1.6.0</td><br>- * <td>Full-Support</td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk 1.6.1</td><br>- * <td>/branches/1.6.1</td><br>- * <td>Full-Support</td><br>- * <td>Still in beta</td><br>- * </tr><br>- * <tr><br>- * <td>Asterisk trunk</td><br>- * <td>/trunk</td><br>- * <td>Full-Development</td><br>- * <td>No releases are made directly from trunk.</td><br>- * </tr><br>- * </table><br>- * \endhtmlonly<br>- *<br>- * For more information on how and when Asterisk releases are made, see the<br>- * release policies page:<br>- * \arg \ref ReleasePolicies<br>- */<br>-<br>-/*!<br>- * \page ReleasePolicies Asterisk Release and Commit Policies<br>- *<br>- * \section releasestatus Asterisk Release Status<br>- *<br>- * For more information on the current status of each Asterisk release series,<br>- * please see the Asterisk Release Status page:<br>- *<br>- * \arg \ref ReleaseStatus<br>- *<br>- * <hr><br>- *<br>- * \section commitmonitoring Commit Monitoring<br>- *<br>- * To monitor commits to Asterisk and related projects, visit <br>- * <a href="http://lists.digium.com/">http://lists.digium.com</a>. The Digium<br>- * mailing list server hosts a %number of mailing lists for commits.<br>- *<br>- * <hr><br>- *<br>- * \section ast10policy Asterisk 1.0<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /branches/1.0<br>- *<br>- * \subsection ast10releases Release and Commit Policy<br>- * No more releases of Asterisk 1.0 will be made for any reason.<br>- *<br>- * No commits should be made to the Asterisk 1.0 branch.<br>- * <br>- * <hr><br>- *<br>- * \section ast12policy Asterisk 1.2<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /branches/1.2<br>- *<br>- * \subsection ast12releases Release and Commit Policy<br>- *<br>- * There will be no more scheduled releases of Asterisk 1.2.<br>- * <br>- * Commits to the Asterisk 1.2 branch should only address security issues or<br>- * regressions introduced by previous security fixes. For a security issue, the<br>- * commit should be accompanied by an <br>- * <a href="http://downloads.asterisk.org/pub/security/">Asterisk Security Advisory</a><br>- * and an immediate release. When a commit goes in to fix a regression, the previous<br>- * security advisory that is related to the change that introduced the bug should get<br>- * updated to indicate that there is an updated version of the fix. A release should<br>- * be made immediately for these regression fixes, as well.<br>- *<br>- * \subsection ast12releasenumbers Release Numbering<br>- *<br>- * - 1.2.X - a release that contains new security fixes<br>- * - 1.2.X.Y - a release that contains fixes to the security patches released in<br>- * version 1.2.X<br>- *<br>- * <hr><br>- *<br>- * \section ast14policy Asterisk 1.4<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /branches/1.4<br>- *<br>- * \subsection ast14releases Release and Commit Policy<br>- *<br>- * Asterisk 1.4 is receiving regular bug fix release updates. An attempt is made to<br>- * make releases of every four to six weeks. Since this release series is receiving<br>- * changes for all types of bugs, the number of changes in a single release can be<br>- * significant. 1.4.X releases go through a release candidate testing cycle to help<br>- * catch any regressions that may have been introduced.<br>- *<br>- * Commits to Asterisk 1.4 must be to address bugs only. No new %features should be<br>- * introduced into Asterisk 1.4 to reduce the %number of changes to this established<br>- * release series. The only exceptions to this %rule are for cases where something<br>- * that may be considered a feature is needed to address a bug or security issue.<br>- *<br>- * \subsection ast14releasenumbers Release Numbering<br>- *<br>- * - 1.4.X - a release that contains new bug fixes to the 1.4 release series<br>- * - 1.4.X.Y - a release that contains very few changes on top of 1.4.X. This<br>- * may be for a security patch, or for a regression introduced in 1.4.X.<br>- *<br>- * <hr><br>- *<br>- * \section ast16policy Asterisk 1.6<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /branches/1.6.*<br>- *<br>- * \subsection ast16releases Release and Commit Policy<br>- *<br>- * Asterisk 1.6 is managed in a different way than previous Asterisk release series.<br>- * From a high level, it was inspired by the release model used for Linux 2.6.<br>- * The intended time frame for 1.6.X releases is every 2 or 3 months. Each 1.6.X<br>- * release gets its own branch. The 1.6.X branches are branches off of trunk.<br>- * Once the branch is created, it only receives bug fixes. Each 1.6.X release goes<br>- * through a beta and release candidate testing cycle.<br>- *<br>- * After a 1.6.X release is published, it will be maintained until 1.6.[X + 3] is<br>- * released. While a 1.6.X release branch is still maintained, it will receive only<br>- * bug fixes. Periodic maintenance releases will be made and labeled as 1.6.X.Y.<br>- * 1.6.X.Y releases should go through a release candidate test cycle before being<br>- * published.<br>- *<br>- * For now, all previous 1.6 release will be maintained for security issues. Once<br>- * we have more 1.6 releases to deal with, this part of the policy will likely change.<br>- * <br>- * For some history on the motivations for Asterisk 1.6 release management, see the<br>- * first two sections of this<br>- * <a href="http://lists.digium.com/pipermail/asterisk-dev/2007-October/030083.html">mailing list post</a>.<br>- *<br>- * \subsection ast16releasenumbers Release Numbering<br>- *<br>- * - 1.6.X - a release that includes new functionality<br>- * - 1.6.X.Y - a release that contains fixes for bugs or security issues identified<br>- * in the 1.6.X release series.<br>- *<br>- * <hr><br>- *<br>- * \section asttrunk Asterisk Trunk<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /trunk<br>- *<br>- * \subsection asttrunkpolicy Release and Commit Policy<br>- *<br>- * No releases are ever made directly from Asterisk trunk.<br>- *<br>- * Asterisk trunk is used as the main development area for upcoming Asterisk 1.6 <br>- * releases. Commits to Asterisk trunk are not limited. They can be bug fixes,<br>- * new %features, and architectural improvements. However, for larger sets<br>- * of changes, developers should work with the Asterisk project leaders to<br>- * schedule them for inclusion. Care is taken not to include too many invasive<br>- * sets of changes for each new Asterisk 1.6 release.<br>- *<br>- * No changes should go into Asterisk trunk that are not ready to go into a<br>- * release. While the upcoming release will go through a beta and release<br>- * candidate test cycle, code should not be in trunk until the code has been<br>- * tested and reviewed such that there is reasonable belief that the code<br>- * is ready to go.<br>- *<br>- * <hr><br>- *<br>- * \section astteam Asterisk Team Branches<br>- *<br>- * \subsection svnbranch SVN Branch<br>- *<br>- * \arg /team/<developername><br>- *<br>- * \subsection astteampolicy Release and Commit Policy<br>- *<br>- * The Asterisk subversion repository has a special directory called "team"<br>- * where developers can make their own personal development branches. This is<br>- * where new %features, bug fixes, and architectural improvements are developed<br>- * while they are in %progress.<br>- *<br>- * Just about anything goes as far as commits to this area goes. However,<br>- * developers should keep in mind that anything committed here, as well as<br>- * anywhere else on Digium's SVN server, falls under the contributor license<br>- * agreement.<br>- *<br>- * In addition to each developer having their own space for working on projects,<br>- * there is also a team/group folder where %group development efforts take place.<br>- *<br>- * Finally, in each developer folder, there is a folder called "private". This<br>- * is where developers can create branches for working on things that they are<br>- * not ready for the whole world to see.<br>- */<br>diff --git a/include/asterisk/doxygen/reviewboard.h b/include/asterisk/doxygen/reviewboard.h<br>deleted file mode 100644<br>index 59ab852..0000000<br>--- a/include/asterisk/doxygen/reviewboard.h<br>+++ /dev/null<br>@@ -1,125 +0,0 @@<br>-/*<br>-* Asterisk -- An open source telephony toolkit.<br>-*<br>-* Copyright (C) 1999 - 2009, Digium, Inc.<br>-*<br>-* See http://www.asterisk.org for more information about<br>-* the Asterisk project. Please do not directly contact<br>-* any of the maintainers of this project for assistance;<br>-* the project provides a web site, mailing lists and IRC<br>-* channels for your use.<br>-*<br>-* This program is free software, distributed under the terms of<br>-* the GNU General Public License Version 2. See the LICENSE file<br>-* at the top of the source tree.<br>-*/<br>-<br>-/*!<br>-* \file<br>-*/<br>-<br>-/*!<br>- * \page Reviewboard Reviewboard Usage and Guidelines<br>- *<br>- * <hr><br>- *<br>- * \section ReviewboardGuidelines Usage Guidelines<br>- *<br>- * Mantis (https://issues.asterisk.org) and Reviewboard (https://reviewboard.asterisk.org)<br>- * are both utilities that the Asterisk development community uses to help<br>- * track and review code being written for Asterisk. Since both systems<br>- * are used for posting patches, it is worth discussing when it is appropriate<br>- * to use reviewboard and when not.<br>- *<br>- * Here are the situations in which it is appropriate to post code to reviewboard:<br>- * - A committer has a patch that they would like to get some feedback on before<br>- * merging into one of the main branches.<br>- * - A committer or bug marshal has requested a contributor to post their patch<br>- * from Mantis on reviewboard to aid in the review process. This typically<br>- * happens with complex code contributions where reviewboard can help aid in<br>- * providing feedback.<br>- *<br>- * We do encourage all interested parties to participate in the review process.<br>- * However, aside from the cases mentioned above, we prefer that all code<br>- * submissions first go through Mantis.<br>- *<br>- * \note It is acceptable for a committer to post patches to reviewboard before<br>- * they are complete to get some feedback on the approach being taken. However,<br>- * if the code is not yet ready to be merged, it \b must be documented as such.<br>- * A review request with a patch proposed for merging should have documented<br>- * testing and should not have blatant coding guidelines violations. Lack of<br>- * these things is careless and shows disrespect for those reviewing your code.<br>- *<br>- * <hr><br>- *<br>- * \section ReviewboardPosting Posting Code to Reviewboard<br>- *<br>- * \subsection postreview Using post-review<br>- *<br>- * The easiest way to post a patch to reviewboard is by using the<br>- * post-review tool. We have post-review in our repotools svn repository.<br>- *<br>- * \verbatim<br>- * $ svn co http://svn.digium.com/svn/repotools<br>- * \endverbatim<br>- *<br>- * Essentially, post-review is a script that will take the output of "svn<br>- * diff" and create a review request out of it for you. So, once you have<br>- * a working copy with the changes you expect in the output of "svn diff",<br>- * you just run the following command:<br>- *<br>- * \verbatim<br>- * $ post-review<br>- * \endverbatim<br>- * <br>- * If it complains about not knowing which reviewboard server to use, add<br>- * the server option:<br>- * <br>- * \verbatim<br>- * $ post-review --server=https://reviewboard.asterisk.org<br>- * \endverbatim<br>- *<br>- * \subsection postreviewnewfiles Dealing with New Files<br>- * <br>- * I have one final note about an oddity with using post-review. If you<br>- * maintain your code in a team branch, and the new code includes new<br>- * files, there are some additional steps you must take to get post-review<br>- * to behave properly.<br>- * <br>- * You would start by getting your changes applied to a trunk working copy:<br>- * <br>- * \verbatim<br>- * $ cd .../trunk<br>- * \endverbatim<br>- * <br>- * Then, apply the changes from your branch:<br>- * <br>- * \verbatim<br>- * $ svn merge .../trunk .../team/group/my_new_code<br>- * \endverbatim<br>- * <br>- * Now, the code is merged into your working copy. However, for a new<br>- * file, subversion treats it as a copy of existing content and not new<br>- * content, so new files don't show up in "svn diff" at this point. To get<br>- * it to show up in the diff, use the following commands so svn treats it<br>- * as new content and publishes it in the diff:<br>- * <br>- * \verbatim<br>- * $ svn revert my_new_file.c<br>- * $ svn add my_new_file.c<br>- * \endverbatim<br>- * <br>- * Now, it should work, and you can run "post-review" as usual.<br>- *<br>- * \subsection postreviewupdate Updating Patch on Existing Review Request<br>- *<br>- * Most of the time, a patch on reviewboard will require multiple iterations<br>- * before other sign off on it being ready to be merged. To update the diff<br>- * for an existing review request, you can use post-review and the -r option.<br>- * Apply the current version of the diff to a working copy as described above,<br>- * and then run the following command:<br>- * <br>- * \verbatim<br>- * $ post-review -r <review request number><br>- * \endverbatim<br>- */<br>diff --git a/include/asterisk/doxyref.h b/include/asterisk/doxyref.h<br>index 5550023..14ebb4b 100644<br>--- a/include/asterisk/doxyref.h<br>+++ b/include/asterisk/doxyref.h<br>@@ -33,12 +33,6 @@<br> *<br> * \section devpolicy Development and Release Policies<br> * \arg \ref CodeGuide : The must-read document for all developers<br>- * \arg \ref CommitMessages : Information on formatting and special tags for commit messages<br>- * \arg \ref ReleaseStatus : The current support level for various Asterisk releases<br>- * \arg \ref ReleasePolicies : Asterisk Release and Commit Policies<br>- * \arg \ref Reviewboard : Reviewboard Usage and Guidelines<br>- * \arg \ref MantisWorkflow : Workflow Guidelines for Asterisk Open Source Issue Tracker<br>- * \arg \ref AsteriskGitHowto : How to setup a local GIT mirror of the Asterisk SVN repository<br> * \arg \ref AstCREDITS : A Thank You to contributors (unfortunately out of date)<br> *<br> * \section apisandinterfaces Asterisk APIs and Interfaces<br></pre><p>To view, visit <a href="https://gerrit.asterisk.org/7269">change 7269</a>. To unsubscribe, visit <a href="https://gerrit.asterisk.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.asterisk.org/7269"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: asterisk </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-MessageType: newchange </div>
<div style="display:none"> Gerrit-Change-Id: Ic072cc8641f9533a202990ccf275ce87e3efd95c </div>
<div style="display:none"> Gerrit-Change-Number: 7269 </div>
<div style="display:none"> Gerrit-PatchSet: 1 </div>
<div style="display:none"> Gerrit-Owner: Corey Farrell <git@cfware.com> </div>