M4 Release Process Notes has been edited by Rafael H. Schloming (Jan 08, 2009).

(View changes)

  1. Release notes generated from Jira are incomplete/inaccurate
  2. Release note text files are included in the artifacts, so can only contain things which are known in advanced
  3. Releases shouldn't be scheduled right before the holiday break
  4. Trunk was closed for a long time
  5. Was difficult to know what the status of the release was due to Jira inaccuracies
  6. Lack of clear documentation about release artifacts
  7. Lack of interest in fixing problems with some artifacts
  8. Many java commits unreviewed: jiras randomly set to resolved, sat in in-progress for ages etc.
  9. Addition of GPL library as dependency
  10. branching and tagging conventions are inconsistent across releases
  11. windows build files require manual updates was a problem

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences