It's my pleasure to announce the release of git-review 2.0.0. These
are the corresponding release notes since the previous release:
New Features
------------
* A new gitreview.branchauthor option allows configuring the
change author (owner) name part of the autocreated branch name
when downloading changes.
* A new gitreview.notopic configuration setting makes git-review
always behave as if the --notopic command line option was
supplied.
Upgrade Notes
-------------
* Not really a deprecation so much as a removal, Gerrit 2.15
(released in 2017) ceased providing a draft state for changes,
and many large sites were disabling support for it far earlier
than that. As of now, git-review has removed the -D and --draft
options entirely, and so can no longer push draft changes on old
Gerrit deployments which still allowed them.
* As of this release, git-review no longer supports running under
the Python 2.7 interpreter. The major version component has been
increased accordingly. Users wishing to use git-review with
Python 2.7 can cap their installations like pip install
"git-review<2", though pip version 9 and later will use
python_requires package metadata to avoid installing git-review
on an unsupported interpreter. Future removal of support for
Python 3 minor versions will only result in a minor version
increase for corresponding git-review releases.
Bug Fixes
---------
* The Change-Id generating commit hook is now installed into any
detected Git submodules, so that it will take effect when
creating changes within a submodule and not just in the parent
repository.
* Encoding was corrected for Git credentials, which was previously
causing HTTP authentication to fail under some Python 3
versions.
* Change download functions now preserve any unapplied local edits
on the branch when attempting to reset the worktree.
* The --no-follow-tags option to git push is now used for all
pushes, so that git-review won’t error when encountering a local
tag which is absent from Gerrit.
* For safety, attempts to push a commit with unstaged or
uncommitted changes in the worktree will be caught and an error
reported, rather than leaving it up to git rebase to spot them.
This addresses a situation where users enabling rebase.autostash
would otherwise experience data loss when the test rebase is
subsequently reset.
As always, the latest version of git-review is available from PyPI:
https://pypi.org/project/git-review
Find the updated documentation at its new home:
https://docs.opendev.org/opendev/git-review
And source code can be obtained through the OpenDev Collaboratory:
https://opendev.org/opendev/git-review
Please don't hesitate to follow up through the
service-discuss(a)lists.opendev.org mailing list or in the #opendev
channel on the Freenode IRC network if you have any questions.
--
Jeremy Stanley