cvs-commit-rules.txt 1.3 KB

12345678910111213141516171819202122232425262728
  1. Kamailio git commit rules
  2. =========================
  3. 1. Changing other people's code:
  4. --------------------------------
  5. - send a patch to the code/module mantainer and/or sr-dev
  6. (don't commit changes to code you don't own if you don't have the mantainer's approval)
  7. Exceptions:
  8. a. compilation (this includes warning) fixes
  9. b. bug fixes
  10. c. API changes (some external functions definitions change)
  11. d. small changes due to a new release in the very near future (allowed only for the release manager)
  12. 2. Code requirements
  13. --------------------
  14. 2.1 Unstable branch:
  15. - the code must compile (at least on one architecture). If the code does not compile,
  16. but you still want to commit it, comment it out (#if 0 ... #endif)
  17. - the code should compile without warnings (with -Wall) (exceptions: very difficult to avoid warnings)
  18. - follow Kamailio coding style
  19. 2.2. Stable branch (everything for unstable branch +)
  20. ------------------------------------------------------
  21. - the code should compile on all the architectures (this currently includes
  22. linux, freebsd, netbsd, openbsd, solaris >= 8; x86, ultrasparc, strongarm;
  23. gcc 4.x, icc, sun cc >=5.3). It should also compile on gcc 2.95 and 3.x.
  24. - the code must be tested or the change trivial enough
  25. - the code should compile without warnings on all the arhitectures (with some exceptions)