That may be deleted, but the code review summary definitely did *not* have the latest version of my changes.
The basic summary is that it changes
bzr 2.0
into
bzr 2.0.0
Which effects things like
bzr 2.1b1 => 2.1.0b1
It also updates cycle.txt and NEWS, etc for these changes.
This is supposed to land in the 2.0.0 release, so that doing:
bzr --version
Properly reports 2.0.0 rather than just 2.0.
(And now that we don't have the simple 'Resubmit' option, I really have no clue what the proper hoops I'm supposed to jump through to get the diff to update... :(
https:/ /code.edge. launchpad. net/~jameinel/ bzr/2.0- full-version/ +merge/ 11617
That may be deleted, but the code review summary definitely did *not* have the latest version of my changes.
The basic summary is that it changes
bzr 2.0
into
bzr 2.0.0
Which effects things like
bzr 2.1b1 => 2.1.0b1
It also updates cycle.txt and NEWS, etc for these changes.
This is supposed to land in the 2.0.0 release, so that doing:
bzr --version
Properly reports 2.0.0 rather than just 2.0.
(And now that we don't have the simple 'Resubmit' option, I really have no clue what the proper hoops I'm supposed to jump through to get the diff to update... :(