This is an archive of the discontinued Mercurial Phabricator instance.

Differential D10500

relnotes: copy contents of "next" to "5.8" and clear "next"
ClosedPublic

Authored by martinvonz on Apr 20 2021, 11:28 AM.

Download Raw Diff

Details

Reviewers

Alphare

Group Reviewers

hg-reviewers

Commits

rHG32b527417ba3: relnotes: copy contents of "next" to "5.8" and clear "next"

Summary

The same procedure as every year^Wcycle.

Unlike previous cycles, I haven't actually recorded the copy because
we don't want to propagate further changes in "next" (from the stable
branch) to "5.8".

Diff Detail

Repository

rHG Mercurial

Lint

Automatic diff as part of commit; lint not applicable.

Unit

Automatic diff as part of commit; unit tests not applicable.

Event Timeline

martinvonz created this revision.Apr 20 2021, 11:28 AM

Herald added a reviewer: hg-reviewers. · View Herald TranscriptApr 20 2021, 11:28 AM

Herald added a subscriber: mercurial-patches. · View Herald Transcript

martinvonz retitled this revision from relnotes: copy "next" to "5.8" and clear "next" to relnotes: copy contents of "next" to "5.8" and clear "next".Apr 20 2021, 11:43 AM

martinvonz edited the summary of this revision. (Show Details)

martinvonz updated this revision to Diff 27132.

Hmm, this will conflict D10496 etc (which I assume are meant for the stable branch just like this patch is). I'm fine with that series or this patch getting queued first. Actually, take that series first since it touches the file several times (I'll just have to resolve the conflict once while @marmoute would have to resolve it several times).

I've taken @marmoute 's series first as you suggested, you can rebase yours now. Thanks for noticing!

This revision now requires changes to proceed.Apr 21 2021, 8:34 AM

martinvonz updated this revision to Diff 27195.Apr 28 2021, 2:16 PM

Alphare accepted this revision.Apr 29 2021, 10:58 AM

This revision is now accepted and ready to land.Apr 29 2021, 10:58 AM

martinvonz added a commit: rHG32b527417ba3: relnotes: copy contents of "next" to "5.8" and clear "next".Apr 29 2021, 11:27 AM

Closed by commit rHG32b527417ba3: relnotes: copy contents of "next" to "5.8" and clear "next" (authored by martinvonz). · Explain Why

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

			Path	Packages
A	M		relnotes/5.8 (68 lines)
M			relnotes/next (47 lines)

Diff	ID	Description	Created	Lint	Unit
Base		Base
Diff 1	27130		Apr 20 2021, 11:28 AM	★	★
Diff 2	27132		Apr 20 2021, 11:43 AM	★	★
Diff 3	27195		Apr 28 2021, 2:16 PM	★	★
Diff 4	27199	rHG32b527417ba3238598859cc43c369caa46faa9c1	Apr 20 2021, 11:28 AM	★	★

Diff 27199

relnotes/5.8

This file was added.

				== New Features ==

				* `hg purge` is now a core command using `--confirm` by default.

				* The `rev-branch-cache` is now updated incrementally whenever changesets
				are added.

				* The new options `experimental.bundlecompthreads` and
				`experimental.bundlecompthreads.<engine>` can be used to instruct
				the compression engines for bundle operations to use multiple threads
				for compression. The default is single threaded operation. Currently
				only supported for zstd.

				== Default Format Change ==

				These changes affects newly created repositories (or new clone) done with
				Mercurial 5.8.

				* The `ZSTD` compression will now be used by default for new repositories
				when available. This compression format was introduced in Mercurial 5.0,
				released in May 2019. See `hg help config.format.revlog-compression` for
				details.

				* Mercurial installation built with the Rust parts will now use the
				"persistent nodemap" feature by default. This feature was introduced in
				Mercurial 5.4 (May 2020). However Mercurial instalation built without the
				fast Rust implementation will refuse to interract with them by default.
				This restriction can be lifted through configuration.

				See `hg help config.format.use-persistent-nodemap` for details

				== New Experimental Features ==

				* There's a new `diff.merge` config option to show the changes
				relative to an automerge for merge changesets. This makes it
				easier to detect and review manual changes performed in merge
				changesets. It is supported by `hg diff --change`, `hg log -p`
				`hg incoming -p`, and `hg outgoing -p` so far.


				== Bug Fixes ==

				* gracefully recover from inconsistent persistent-nodemap data from disk.


				== Backwards Compatibility Changes ==

				* In normal repositories, the first parent of a changeset is not null,
				unless both parents are null (like the first changeset). Some legacy
				repositories violate this condition. The revlog code will now
				silentely swap the parents if this condition is tested. This can
				change the output of `hg log` when explicitly asking for first or
				second parent. The changesets "nodeid" are not affected.


				== Internal API Changes ==

				* `changelog.branchinfo` is deprecated and will be removed after 5.8.
				It is superseded by `changelogrevision.branchinfo`.

				* Callbacks for revlog.addgroup and the changelog._nodeduplicatecallback hook
				now get a revision number as argument instead of a node.

				* revlog.addrevision returns the revision number instead of the node.

				* `nodes.nullid` and related constants are being phased out as part of
				the deprecation of SHA1. Repository instances and related classes
				provide access via `nodeconstants` and in some cases `nullid` attributes.

relnotes/next

	== New Features ==			== New Features ==

	* `hg purge` is now a core command using `--confirm` by default.

	* The `rev-branch-cache` is now updated incrementally whenever changesets
	are added.

	* The new options `experimental.bundlecompthreads` and
	`experimental.bundlecompthreads.<engine>` can be used to instruct
	the compression engines for bundle operations to use multiple threads
	for compression. The default is single threaded operation. Currently
	only supported for zstd.

	== Default Format Change ==			== Default Format Change ==

	These changes affects newly created repositories (or new clone) done with			These changes affects newly created repositories (or new clone) done with
	Mercurial 5.8.			Mercurial 5.8.

	* The `ZSTD` compression will now be used by default for new repositories
	when available. This compression format was introduced in Mercurial 5.0,
	released in May 2019. See `hg help config.format.revlog-compression` for
	details.

	* Mercurial installation built with the Rust parts will now use the
	"persistent nodemap" feature by default. This feature was introduced in
	Mercurial 5.4 (May 2020). However Mercurial instalation built without the
	fast Rust implementation will refuse to interract with them by default.
	This restriction can be lifted through configuration.

	See `hg help config.format.use-persistent-nodemap` for details

	== New Experimental Features ==			== New Experimental Features ==

	* There's a new `diff.merge` config option to show the changes
	relative to an automerge for merge changesets. This makes it
	easier to detect and review manual changes performed in merge
	changesets. It is supported by `hg diff --change`, `hg log -p`
	`hg incoming -p`, and `hg outgoing -p` so far.


	== Bug Fixes ==			== Bug Fixes ==

	* gracefully recover from inconsistent persistent-nodemap data from disk.


	== Backwards Compatibility Changes ==			== Backwards Compatibility Changes ==

	* In normal repositories, the first parent of a changeset is not null,
	unless both parents are null (like the first changeset). Some legacy
	repositories violate this condition. The revlog code will now
	silentely swap the parents if this condition is tested. This can
	change the output of `hg log` when explicitly asking for first or
	second parent. The changesets "nodeid" are not affected.


	== Internal API Changes ==			== Internal API Changes ==

	* `changelog.branchinfo` is deprecated and will be removed after 5.8.
	It is superseded by `changelogrevision.branchinfo`.

	* Callbacks for revlog.addgroup and the changelog._nodeduplicatecallback hook
	now get a revision number as argument instead of a node.

	* revlog.addrevision returns the revision number instead of the node.

	* `nodes.nullid` and related constants are being phased out as part of
	the deprecation of SHA1. Repository instances and related classes
	provide access via `nodeconstants` and in some cases `nullid` attributes.