Merge lp:~abentley/launchpad/bzr-2.2.2-lp-1 into lp:launchpad
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 12166 | ||||
Proposed branch: | lp:~abentley/launchpad/bzr-2.2.2-lp-1 | ||||
Merge into: | lp:launchpad | ||||
Diff against target: |
13 lines (+2/-1) 1 file modified
versions.cfg (+2/-1) |
||||
To merge this branch: | bzr merge lp:~abentley/launchpad/bzr-2.2.2-lp-1 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Edwin Grubbs (community) | code | Approve | |
Benji York (community) | code* | Approve | |
Review via email: mp+45258@code.launchpad.net |
Commit message
[r=benji,
Description of the change
= Summary =
Bzr 2.2.2 is the current stable release, but has some deficiencies that are
fixed in the lp:bzr/2.2 branch, including #687653 "infinite recursion
trying to format NotBranchError" and #681885 "Spurious 'properties changed'
line on incremental diffs".
== Proposed fix ==
Since we need these fixes urgently (#687653 is already a cowboy), I've taken
tip, updated the version number, and called it "2.2.2-lp-1".
== Pre-implementation notes ==
Done at thumper's request
== Implementation details ==
As always, this requires hacking setup.py to specify a static version, because
bzr's internal version numbering doesn't support versions like "2.2.2-lp-1".
== Tests ==
bin/test -v
== Demo and Q/A ==
Hard to say. Bug #687653 doesn't seem to indicate how to reproduce the
problem.
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
versions.cfg
./versions.cfg
237: Line exceeds 78 characters.
Approved.
I did not review the bzr changes, but am instead assuming that the bzr
guys' review caught anything that I would have.
Regarding making the needed changes to the bzr 2.2 tip verses applying
just the changes we need to the version of bzr we currently use: If the
tests pass, I'd rather track 2.2 than diverge further from it because I
have no reason not to believe that the bzr guys make reasonable
decisions in choosing what changes to make there (i.e., low risk bug
fixes). I am not aware of any policy we have regarding this.