I agree here. +1 for Service Release. <div class="gmail_quote">On Nov 29, 2007 10:07 AM, Thomas Mashos <<a href="mailto:thomas@weilandhomes.com">thomas@weilandhomes.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I don't have a problem with it, although I wish we didn't have to do it. I do think that it is a necessary evil though and wont cause too much confusion.  Perhaps for the next cycle we'll have more testers and get more bug reports (or better bug reports). Lets just make sure that if we do, that current users only need to enable that repo, and that this is more of a mythbuntu 7.10-fixes. although adding fixes sounds bad.  Maybe Mythbuntu 7.10+backports and a BOLD snippet that says current users just need to enable that repo. +1 for 7.10.1, but just once. Thomas <div><div></div><div class="Wj3C7c"> On Wed, 2007-11-28 at 23:55 -0600, Mario Limonciello wrote: > Hi Everyone: > > After seeing a lot of issues on the forums cropping up over and over, I > was considering doing a follow up release. > > This follow up release could reflect some of the bigger bugs that were > discovered, such as the mythtv pvr-350 output problems, the pvr-350 lirc > configuration, requiring the CD to install a few things after install, > and anything else that we have (or would like to backport back from > hardy).  At very least, it would make sure that these things aren't > posted on the forums and forced to be marked duplicate time and time again. > > As long as we make it clear that all of these things are available via > the backports repository as well, I think it would probably be a good idea. > > What do people think? > -- </div></div>Ubuntu-mythtv mailing list <a href="mailto:Ubuntu-mythtv@lists.ubuntu.com"> Ubuntu-mythtv@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv</a> </blockquote> </div>