On Thu, Apr 8, 2010 at 6:12 PM, Toshio Kuratomi <a.badger(a)gmail.com> wrote:
I have a bit of a quandry with the bzr package in EPEL I want to
upgrade it
due to compatibility problems but the upgrade brings in abackwards
compatibility problems. Let me explain::
bzr is a distributed version control system. The main hosts of bzr
repositories that we care about are launchpad and
fedorahosted.org. People
can, of course run their own repositories.
So what's this mean for us? It means that I'd like to update
EPEL's bzr to
the 2.1 branch. This breaks API compatibility but it has the following
benefits:
* It brings us over-the-wire compatibility with bzr-2.x
* It brings us repository format compatibility with current bzr-2.x users so
they can share their repositories with users of the EPEL packages
* It brings us a client that can talk to launchpad, probably the most
important source of bzr repositories if you're an open source developer.
So what do other people think here? Is the over-the-wire and
repository-format compatibility issues sufficient to override the API
compatibility issues in this case? As the maintainer, I definitely believe
so but I await your input.
I am +1 to updating to newer version with a cut and release day of XYZ
to be announced and documented. My reasons are:
1) Update to one that works with main bzr sites (launchpad).
2) Allows for fedorahosted to be updated to something that F13 can use.
--
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning