[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: when a non-backward compatible package upgrade is warranted and how

From: Joe Orton <jorton_at_redhat.com>
Date: 2004-06-09 15:46:16 CEST

On Wed, Jun 09, 2004 at 08:27:10AM -0500, Travis P wrote:
> On Jun 9, 2004, at 3:46 AM, Joe Orton wrote:
> >And I say again: it is *never* expected that a package update breaks
> >anything which was supposed to be working before. There needs to be a
> >very good reason to break that rule, and "oh, but this new version is
> >*so* much better" is not good enough IMO.
> Certainly. In this case, wasn't 1.0.3 a significant security fix?

Significant in severity perhaps, but not significantly difficult to fix
with a backported patch to necessitate a schema-breaking-update, given
that the fix is the prudent placement of two extra '3' characters.




To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 9 15:47:38 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.