[mythtv] What can packagers/distro developers do to help the stability of "released" version of MythTV?

[Nav Jagpal]

I haven't done any MythTV development. I'm just giving my two cents.

I know that maintaining multiple branches can be a lot of work. But,
maybe we can take philosophies from other OSS communities.

For example, Debian has three "branches" (Don't think that's the right
word for it).. Stable/testing/unstable. That may be overkill for this
project, but the idea is there.

Correct me if I am wrong, but if we applied a similiar Linux-type
development process to MythTV..

1. You just released .17
2.  Assign someone to be the maintainer of .17
3.  Start development of .18. Any critical fixes are merged into .17
right away (17.1 etc) (for the maintainer of .17 to take care of)
4.  New features do NOT go into .17
5.  Anyone who just wants bug fixes can upgrade to newest version of
.17. Bleeding-edge can be the development of .18.

Would this be too much to handle? I would certainly like to get bug
fixes when they are available if they won't break my existing stable
system.

Thanks.

On Wed, 23 Feb 2005 18:14:37 -0600 (CST), Mark Matula
<mmatula at ratula.net> wrote:
> On Wed, 23 Feb 2005, Isaac Richards wrote:
> 
> > Ah, but you're missing bugzilla:
> > http://www.mythtv.org/bugs/show_bug.cgi?id=225
> 
> Without meaning to sound at all like a smart-ass, a direct link on the
> mythtv.org home page might be cool.  I say this because although there's a
> link in the "Documentation" link, if one clicks on "Topics" and checks out
> out the "Bug Watch" in there, it's pretty disheartening.
> 
> --
> Mark Matula
> Mikey, you will be missed:
> http://eblo.ratula.net/mikey.html
> 
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> 
> 
>