Re: Bug in last release is fixed in CVS - what to do?
On Mon, Jul 21, 2003 at 12:11:46PM +0200, Marcin Juszkiewicz wrote:
> I packaged ROX-Filer (http://rox.sf.net/). Some time ago version 2.0.0 was
> released as stable so I changed few things in packaging. Now I have 3
> packages:
>
> 1. rox - "stable release only" version of ROX-Filer
> 2. rox-snapshot - CVS snapshot of development version
> 3. rox-filer-hrw - rox-snapshot with few extra patches (some of them will not
> be applied by upstream).
>
> Some time ago there was a bug which renders program unusable in current 'sid'
> - it was fixed in CVS version so packages other then "rox" are free from it.
> But not "rox" :( which is used by some people.
>
> What I should do now?
IMO, it depends on whether the bugfix is fairly self-contained, and/or
whether the CVS version is almost a real release/is fairly stable.
If CVS is stable and the fix for the nasty bug is complex, it might be
reasonable to make CVS your new stable - versioning it appropriately.
Otherwise, you'd be better off backporting the patch to your stable version
and releasing that, because it'll surprise users less.
The backport method is the Debian way - look at security releases - but
ephemeral software in sid is different to stable security updates, so the
rules aren't quite the same...
- Matt
Reply to: