RELEASING 1.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. NOTES ON RELEASING NEW VERSION OF NAGIOSPLUG
  2. cvs update in main area
  3. . tools/devmode, if feeling adventurous
  4. check compilation
  5. Update BUGS file, if this is a major release
  6. Run cvs2cl.pl
  7. commit new ChangeLog
  8. Check configure.in with right version
  9. cvs tag r1_4-alpha2
  10. If a main release (eg, non alpha/beta), branch here:
  11. cvs tab -b r1_4-patches
  12. Consider the SF snapshot branches - should you remove any other branches?
  13. checkout new version:
  14. cd /tmp
  15. rm -fr nagiosplug
  16. cvs -z3 -d:ext:tonvoon@cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4-alpha2 nagiosplug
  17. cd nagiosplug
  18. tools/setup
  19. ./configure
  20. make dist
  21. ftp upload.sf.net
  22. anonymous/email
  23. bin
  24. cd /incoming
  25. put file
  26. SF -> Submit News about release.
  27. Get URL to news item
  28. SF -> Admin -> File Releases
  29. Add a release to nagiosplug and create a file release
  30. name: 1.4-alpha2. Commit
  31. Step 1: Add release notes pointing to news item
  32. Step 2: add file
  33. Step 3: *.tar.gz, Platform Independent, Source .gz
  34. Step 4: Send notice
  35. Send email to nagiosplug-help, nagios-announce
  36. Change to next version number in configure.in and package.def