[mythtv] 'stable' tag proposal

[Frank Riley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

J. Donavan Stanley wrote:
> andrew burke wrote:
> 
> 
>>Look, it's common courtesy to bring up issues I have before I go and just
>>fork the code.  Forking a project can often cause lots of bad blood and
>>problems.  I do appreciate what all the devs have put together, I just
>>think that things can be handled a bit differently to improve the end-user
>>experience.  I never said what the developers have done isn't worthwhile,
>>but I do take issue with the way the project is being managed.  I offered
>>to help improve that situation numerous times, and the devs seem to have
>>decided it isn't help they're interested in, and that's their choice.  But
>>personally, I know I would be upset if someone forked a project I started
>>without at least raising the issues they had for doing so.
>> 
>>
> 
> 
> The VAST majority of end users don't use CVS. So it has zero impact on
> them.  You act like every release is some bug ridden piece of shit or
> something. Hell CVS Myth is a heck of a lot more stable than many
> "stable" branches of other projects I've seen.

I don't think the releases are "pieces of shit", but the problem is when
there is a bug in them a user has 2 options: 1) live with it until the next
release or 2) move to CVS to get the fix. I switched to CVS when the .16
release came out because it had bugs in it that I couldn't live with. The
.17 release was the same (try using a 350 for out and doing ff/rew in live
tv with the .17 release). I also do development for a living, and every
place I've worked has a model similar to what Andrew is suggesting. I
honestly don't understand why it is such a big deal. It doesn't add much
overhead, and as Andrew pointed out, would probably make life easier for
people who are overwhelmed now. There seems to be a lot of argument about
not caring about the users. I think some people are missing the point. In my
experience, a model like this makes life easier for *devs* as well.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCP3/J91+pr0EM9zgRAqzDAJ9bZ8R0KE6ib88Ubi9mkVd8l4wAVACfUgVC
wO8jCAeKev8cY67hp/Y+Cog=
=5c5X
-----END PGP SIGNATURE-----