[mythtv] New Install - 0.16 or CVS?
Joseph A. Caputo
jcaputo1 at comcast.net
Sun Oct 31 03:10:36 UTC 2004
On Sat, 30 Oct 2004 20:58:35 +0200
Jesper Sörensen <jesper at datapartner.se> wrote:
> Jeff Thompson wrote:
>
> > A common approach is to create a branch for a released version for
> > fixes (ie. release-0-16-fixes) and allow new development to continue
> > on the HEAD. True, this does cause additional work for the
> > developers/maintainers to ensure that you don't reintroduce bugs by
> > forgetting to merge changes from the fixes branch to the HEAD, but
> > it has the advantage that the most stable release of the product is
> > always available.
>
>
> You are correct, it would be nice with a stable branch in CVS, but you
> are also correct in the fact that it would require "someone" to do the
> work. I don't know if you're volunteering to do it but personally I
> don't think it's that big of a problem and I would rather see that the
> developers spent their time on improving Myth or fixing more bugs
> (instead of fixing it twice, on different branches in CVS... ;-)
>
> If there are serious bugs/problems with a release, Isaac would
> probably make an extra bugfix release (as was the case with 0.15.1),
> and you could always backport fixes on a case by case basis. Many
> patches posted on the dev list should apply cleanly to both CVS and
> the last stable release. If you can't do it yourself, I'm sure you
> could get some help if you ask nicely.
Also, don't forget that Myth, although pretty stable and quite usable,
is still pre-1.0. Maybe when we reach v.1.0 (whenever that may be), it
would then be more compelling to maintain a 'stable' branch. (Of
course, based on the current version numbering scheme, one wonders if a
"1.0" version is even planned... personally I could care less what the
version number is; I've been using CVS HEAD for 2 years 24x7 with never
a problem, upgrading every few weeks at least).
-JAC
More information about the mythtv-dev
mailing list