<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebAccess v6.04-11575">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<title>RE: Re: So many repo formats</title>
<style type="text/css">
body
{
font-family: Arial, Verdana, Sans-Serif;
font-size: 12px;
padding: 5px 5px 5px 5px;
margin: 0px;
border-style: none;
background-color: #ffffff;
}
p, ul, li
{
margin-top: 0px;
margin-bottom: 0px;
}
</style>
</head>
<body>
<p> </p><p>-----Original message-----</p><br /><blockquote style="border-left: 2px solid rgb(50, 95, 186); padding-left: 5px; margin-left: 5px;"><strong>From:</strong> Stephen J. Turnbull <stephen@xemacs.org><br /><strong>Sent:</strong> Wed 11/19/08 03:17:16<br /><strong>To:</strong> Gour <gour@mail.inet.hr>; <br /><strong>CC:</strong> bazaar@lists.canonical.com; <br /><strong>Subject:</strong> Re: So many repo formats<br /><br />Gour writes:<br /><br /> > So, I understand you could have many old branches laying around, but do<br /> > not understand what's the problem to fire up some small script and<br /> > upgrade all those repos?<br /><br />Well, actually, you can't understand. What you can understand is that<br />it *does* annoy other bzr "customers", for reasons only they can give<br />(that's why *we* can't give you a full explanation), so bzr shouldn't<br />force upgrades of repos that aren't currently in use. It should find<br />another way to simplify the interface for you.<br /><br />N.B. This is quite a different thing from forcing upgrades of in-use<br />repos: the customer has a choice of not upgrading bzr if the features<br />in the new version don't outweigh the annoyance of upgrading in-use<br />repos. But if you de-support old repos, then the customer must<br />document the need for and maintain the old version (which can be<br />painful, less so with a Python app like bzr, but it's still not<br />trivial) or *find* all the relevant repos and upgrade them while you<br />still can.<br /><br />There are yet other workarounds, of course, but they all involve<br />imposing unnecessary work on people who don't want to do it. Not a<br />good way to garner support for your tool.<br /><br /></blockquote><p>Use case:</p><p>Joe's project X seems to be finished so he makes a final release and backs up the repos to an archive (e.g. DVD or tape). </p><p> </p><p>2 years later project X needs to be resurrected (not so unusual, I've seen this several times over the last few years). Manager gives me the DVD and says get on with it.</p><p> </p><p>I restore the backup. I now have a repos with a format that is at least 2 years old. But oh dear! Because of Gour's proposal that format is no</p><p>longer supported by bazaar :(((</p><p> </p><p> </p>
</body>
</html>