I'll add an item to the agenda right away... Thanks... Dave
From: [email protected] <[email protected]> On Behalf Of Ole Troan
Sent: Tuesday, May 21, 2019 1:43 PM
To: vpp-dev <[email protected]>
Subject: [vpp-dev] Process improvement proposal 3/3 - commit criteria
This is the third of three proposals for process changes.
This is a proposed "checklist" of (feature) commit critiera. It would be
expected that new features should adhere to this list.
I am not proposing any tooling around this list, it would be VPP committers /
community policing.
VPP Commit Criteria
Testing
Unit testing (C based)
Feature testing (Python framework)
Performance and scale testing
Multi-worker testing
Code coverage numbers
Documentation
API documentation
.md (aka man page per API message)
Feature/Concept documentation
Documentation of new startup parameters
Feature meta data (FEATURE.yaml)
"User interface"
API
Stats
CLI
Misc
Collateral damage
Not listening on e.g. UDP port without being enabled
No running process without being enabled
Do not create bihash tables or map large chunks of VM when not
enabled.
Leak check
Valgrind
Static analysis
Code review
Status
Experimental (e.g. plugin disabled by default
Production
Comments are welcome!
(I will also ask for time at next weeks community call)
Best regards,
Ole
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13108): https://lists.fd.io/g/vpp-dev/message/13108
Mute This Topic: https://lists.fd.io/mt/31699471/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
