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

Jean-Yves Avenard jyavenard at gmail.com
Fri Jan 30 07:08:55 UTC 2009


Hi

2009/1/30 Bill Williamson <bill at bbqninja.com>:

> 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.


I totally agree with this ...
In very few places have I seen all new development directly working on
trunk all at the same time instead of each forking on their own and
being merged back.

I certainly wouldn't want any of my developers to start working on a
project that way

For some bizarre reason, the myth development team however is doing it
properly for the vid branch... which makes a lot of sense.

>
> 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

But does it make it any easier on the developers however?
so many things get change at the same time that it's very hard to
identify where the problem actually comes from, when it was introduced
etc...

> 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.

You can still think they are doing it wrong however :)


More information about the mythtv-dev mailing list