* Fixed: [State XML validation error when CLICON_MODULE_LIBRARY_RFC7895=true and ietf-yang-libra$
* Removed obsolete option: `CLICON_MODULE_LIBRARY_RFC7895' * Obsolete config options given in the confi file are considered an error * Added section in CONTRIBUTING relating to optimzation * Changed reset merge to implicit default values. * This avoids a potential overwriting of explicitly set default values in the existing config * Adapted some code to [Make cligen_* functions const ](https://github.com/clicon/cligen/pull/83) * Test: fixed test for * Fixed: [datamodel tree generated from basemodel tree is not proper when a list has more than one key and key is of enum type](https://github.com/clicon/clixon/issues/417)
This commit is contained in:
parent
7868cf0a0d
commit
d358387d39
13 changed files with 77 additions and 59 deletions
|
|
@ -4,8 +4,7 @@ The clixon project welcomes contributions from the community.
|
|||
|
||||
## Licensing
|
||||
|
||||
A contribution must follow the [CLIXON
|
||||
licensing](https://github.com/clicon/clixon/blob/master/LICENSE.md)
|
||||
A contribution must follow the [CLIXON licensing](https://github.com/clicon/clixon/blob/master/LICENSE.md)
|
||||
with the dual licensing: either Apache License, Version 2.0 or
|
||||
GNU General Public License Version 3.
|
||||
|
||||
|
|
@ -138,3 +137,16 @@ include:
|
|||
- [CI on other platforms](https://github.com/clicon/clixon/tree/master/test/cicd). Other platforms include x86-64, 32-bit i686, and armv71
|
||||
- [Coverage tests](https://app.codecov.io/gh/clicon/clixon)
|
||||
- [Fuzzing](https://github.com/clicon/clixon/tree/master/test/fuzz) Fuzzing are run occasionally using AFL
|
||||
|
||||
## Optimization
|
||||
|
||||
Optimizating Clixon code should be based on an observable improvement
|
||||
of measurements of cycles or memory usage.
|
||||
|
||||
Usually, new clixon code starts out with functional compliance
|
||||
with appropriate regression tests.
|
||||
|
||||
Therafter "non-functional" analysis, including performance tests can
|
||||
be made. Performance improvements should be based on specific usecase
|
||||
and actual measurement. The benefit of an optimization should
|
||||
be larger than a potential increase of complexity.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue