When you have changes that you’d like to be included in the INET Framework, here is the process:
masterbranch. If the target branch has moved on in the meantime, rebase your topic branch on top of it
A good commit message helps future INET maintainers find out why a particular change was made to the code, and determine its correctness.
tcp:). Such prefix is immensely helpful for people browsing the project history. In some cases, using a topic word instead of the component name may also be justifiable (e.g.
fix:and the bug number (if available).
There will be two reviews: semantic and technical review.
The semantic review will be performed by advisors of the affected component, and will include:
The technical review will be done by the core team:
.oppfeatures, and adding smoke/fingerprint tests can be left to the core team