[mythtv] Ticket #5487: LATM AAC audio stream support

Bill Williamson bill at bbqninja.com
Fri Jan 30 06:00:33 UTC 2009


On Fri, Jan 30, 2009 at 3:13 PM, David Engel <david at istwok.net> wrote:

> On Thu, Jan 29, 2009 at 06:45:21PM +0000, Paul Harrison wrote:
> >> Comment(by jyavenard at gmail.com):
> > Please don't take this as a criticism but an observation. If you spent
> > half the time  you have on backporting stuff to fixes instead on fixing
> > the segfaults or problem you say you had with trunk then we'd be that
> > much nearer to releasing 0.22 which I hope is what everyone wants.
>
> Is there an agreed upon list of remaining tasks for 0.22 and is that
> list short enough to give any hope of a release in the near term?  I
> can't speak for anyone else, but my interest in working on trunk would
> probably increase if the answers are yes.  I'd love to help stabilize
> the HD-PVR and VDPAU support, but if there's several more months of UI
> porting to be done before it's ready for production use, I'd rather
> spend my free time elsewhere.
>
> To the guys working on the new UI, please don't take the above as a
> knock.  It does look pretty.  It's just not a feature that inerests
> me.
>
>
Coming from a development background the big "issue" people are having is
that myth is a "dev is the trunk, stable is a branch" methodology instead of
a "trunk is main, features are branched" one.

For example, the way many other projects would be run is that trunk would
remain stable.  VDAPU would be a branch (kept compatible against trunk) and
once it was ready it would be merged back in.  Same with HD-PVR, the new
mythui support, etc.

Instead, with the current model ALL new features must be "ready" at the same
time or else NONE can be released.  It makes less headache for the project
lead (no messy repatching of all the branches when a new feature is merged
to trunk, no infighting for who "goes to trunk" first, etc), though, and
ensures that once a release happens the ENTIRE release has been
orchestrated.

I've worked in professional places that have done both, so this isn't a
"mythtv devs are doing it wrong" post.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20090130/89af95ca/attachment.htm>


More information about the mythtv-dev mailing list