[ubuntu-mythtv] upstream mythtv 0.22 branch created

[Marc Randolph]

Howdy all,

Just in time for the last Mythbuntu alpha, upstream has branched 0.22.
 For those that care to pull the source directly, here it is handy for
copy and paste:

svn co http://svn.mythtv.org/svn/branches/release-0-22-fixes

Now that I think about it, it's kinda unfortunate that the word
"trunk" is in the mythbuntu ppa name... people will need to manually
change which ppa they track, right?  Maybe next time it could just be
named 0.23 so that it can automatically migrate from being "trunk" to
being on the branch?

There are still 104 bugs targeted for 0.22 open upstream, although the
vast majority are minor.  That's double the number they had 0.21 was
branched, but considering most are minor, I strongly suspect they'll
call it complete before 9.10 ships.

Speaking of which, there are only 6 weekends left before 9.10 walks
out the door.  We've done a decent job of cutting down the bugs on the
Launchpad side of things...

Only 29 bugs (not marked incomplete) in the Mythtv bucket:
<<https://bugs.launchpad.net/ubuntu/+source/mythtv/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY>>

and the Mythbuntu bucket has 90 bugs (not marked incomplete, and not
marked wishlist):
<<https://bugs.launchpad.net/mythbuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY>>

Some of these you all had identified solutions for... so I'll bet a
number can still be closed out relatively easily!

   Marc