D6332: releasenotes: add a file in which to record release-notes

martinvonz (Martin von Zweigbergk) phabricator at mercurial-scm.org
Thu May 2 00:04:59 EDT 2019


martinvonz created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.

REVISION SUMMARY
  I've just spent a few very boring hours going through the changelog
  for the 5.0 release (829 commits). We only had 5 commits that used the
  syntax that the release notes extension expects. This commit adds a
  file in which we can record important changes. The file should
  preferably be edited in the patch that makes the important change, but
  it can also be edited after (I think this is an important benefit
  compared to the release notes extension).
  
  I'm thinking that we can rename the file from "next" to "5.1" or
  something when it's time, and then we'd create a new "next" file on
  the default branch.
  
  I've used the syntax that we use on the our wiki in the template, but
  I don't care much that we use any valid syntax at all. The idea is
  mostly to record important changes when they happen. I expect that
  some copy editing will be needed at release time anyway.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D6332

AFFECTED FILES
  release-notes/next

CHANGE DETAILS

diff --git a/release-notes/next b/release-notes/next
new file mode 100644
--- /dev/null
+++ b/release-notes/next
@@ -0,0 +1,10 @@
+== New Features ==
+
+
+== Bug Fixes  ==
+
+
+== Backwards Compatibility Changes ==
+
+
+== Internal API Changes ==



To: martinvonz, #hg-reviewers
Cc: mercurial-devel


More information about the Mercurial-devel mailing list