jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Terminology correction in html docs

Browse source
This commit is contained in:
William S Fulton 2019-02-09 18:02:55 +00:00
commit 3e4b0aace8
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Doc/Manual/Extending.html
View file

@ -3626,7 +3626,7 @@ A target language is given the 'Experimental' status when
<ul> <ul>
<li> <li>
It is of sub-standard quality, failing to meet the above 'Standard' status. It is of sub-standard quality, failing to meet the above 'Supported' status.
</li> </li>
<li> <li>
It is somewhere between the mid to mature stage of development. It is somewhere between the mid to mature stage of development.
@ -3652,7 +3652,7 @@ Some minimum requirements and notes about languages with the 'Experimental' stat
Have fully functional examples of basic functionality (the simple and class examples). Have fully functional examples of basic functionality (the simple and class examples).
</li> </li>
<li> <li>
The test-suite must be implemented and include some runtime tests for wrapped C and C++ tests. The test-suite must be implemented and include a few runtime tests for both C and C++ test cases.
</li> </li>
<li> <li>
Failing tests must be put into one of the FAILING_CPP_TESTS or FAILING_C_TESTS lists in the test-suite. Failing tests must be put into one of the FAILING_CPP_TESTS or FAILING_C_TESTS lists in the test-suite.
@ -3668,7 +3668,7 @@ Some minimum requirements and notes about languages with the 'Experimental' stat
Any new failed tests will be fixed on a 'best effort' basis by core developers with no promises made. Any new failed tests will be fixed on a 'best effort' basis by core developers with no promises made.
</li> </li>
<li> <li>
If a language module has an official maintainer, then the maintainer will be requested to focus on fixing test-suite regressions and commit to migrating the module to become a 'Standard' module. If a language module has an official maintainer, then the maintainer will be requested to focus on fixing test-suite regressions and commit to migrating the module to become a 'Supported' module.
</li> </li>
<li> <li>
If a module does not have an official maintainer, then, as maintenance will be on a 'best efforts' basis by the core maintainers, no guarantees will be provided from one release to the next and regressions may creep in. If a module does not have an official maintainer, then, as maintenance will be on a 'best efforts' basis by the core maintainers, no guarantees will be provided from one release to the next and regressions may creep in.