1.14 is now quite old, and if we're going to do any backports it should be of 2.0.x.
2.0.x has been out and quite stable for about four months, and 2.0.2 has now got into karmic-updates, through an SRU for <https://bugs.edge.launchpad.net/ubuntu/+source/bzr/+bug/437626>. It would be appropriate to backport from karmic-updates to hardy, intrepid, etc. I think this bug is effectively a dupe of bug 487429, asking for 2.0.2 to be backported, so I'll combine them. ** Also affects: jaunty-backports Importance: Undecided Status: New ** Summary changed: - Please backport bzr 1.14 + Please backport bzr 2.0.2 from karmic-updates ** Description changed: - bzr has fixed several bugs, improved performance, and added support for - new formats since the versions in hardy (currently 1.3.1). See for - instance bug 301592. It would be nice to backport the current version, - either 1.6 (from hardy) or the current release from - http://launchpad.net/~bzr/+ppa. + bzr 2.0.2 is a large improvement over the 1.x features shipped in + earlier releases, and includes supports for the 2a repository format + used for ubuntu distributed development and many other branches. + + 2.0.2 has passed through the SRU process into karmic-updates. It would + be good to now backport it into earlier releases. It should build at + least back to hardy with no changes. -- Please backport bzr 2.0.2 from karmic-updates https://bugs.launchpad.net/bugs/302987 You received this bug notification because you are a member of Ubuntu Backports Testing Team, which is subscribed to Hardy Backports. -- ubuntu-backports mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
