RELEASE_PROCEDURE 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. This document describes step by step the release procedure of GNU
  2. Midnight Commander.
  3. ${dotted_version} shall be replaced by something like 4.6
  4. ${underscore_version} shall be replaced by something like 4_6
  5. === day 0 (translator's prerelease) ===
  6. * Check out a fresh copy from the CVS repository.
  7. * Update the translation files NOT to contain line number information.
  8. Commit them.
  9. * Tag the CVS tree as "MC_${underscore_version}_translators".
  10. * Update the translation files to contain line number information.
  11. DON'T commit them.
  12. * Run "make dist".
  13. * Upload the distribution tarballs and the individual translation files
  14. somewhere where the translators can download it.
  15. * Announce the availibility of the translator's prerelease on mc-devel.
  16. Inform the translators of the prerelease.
  17. Inform the developers of a fourteen-day "feature-freeze".
  18. === day 11 (reminder) ===
  19. * announce a reminder on mc-devel that the release will occur in three
  20. days.
  21. === day 14 (official release) ===
  22. * Review the English version of the manual and fix it if necessary.
  23. Update the date and the version number in the .TH macro of the English
  24. manual pages.
  25. * Update the NEWS file to contain all user-visible changes.
  26. * Fix wrong formatting in the ChangeLog files.
  27. * Set the version number in configure.ac to "${dotted_version}".
  28. Commit it.
  29. * Update the translation files NOT to contain line number information.
  30. Commit them.
  31. * Run the test suites maint/mctest and maint/mc-test and make sure
  32. all warnings are ok.
  33. * Tag the CVS tree as "MC_${underscore_version}_release".
  34. * Create a CVS branch "MC_${underscore_version}".
  35. * Run "make dist".
  36. * Upload the resulting tarballs to the Savannah repository.
  37. * Announce the new release on the mc-devel and mc mailing lists.
  38. * Update the homepage.
  39. === post-release actions ===
  40. * Create binary packages from the uploaded tarballs as necessary.
  41. === back to work ===
  42. * Discuss milestones for the next release on the mc-devel list.