[mythtv] MythTV life-cycle support intentions

[Jean-Yves Avenard]

Hi

On 24 July 2012 10:59, Gary Buhrmaster <gary.buhrmaster at gmail.com> wrote:
> Historically, it appears by observation, that "back-porting" fixes
> from master has been mostly limited to (a) what is possible to
> back-port (well, obviously!), and (b) one version.  So, for example,
> during the (to be) 0.26 development cycle, many fixes were
> backported to 0.25, but few to 0.24 (which may be more reflective
> of (a) than anything else).

I personally have backported fixed from master to the latest official
release. But never to the previous release.
Don't see the point, this is not a commercial enterprise...

If people want support, they can update to the latest version.

> With the pending release of 0.26, does this mean that it is likely
> that (with the occasional exception) that fixes in master will
> likely be back-ported only to 0.26 and not 0.25 (and likely never
> 0.24)?

I'd say that's exactly how it's going to be.

We had plan to maintain a backport branch, that includes all the
master backports that do not require a schema or protocol change... I
was supposed to do it, but lack of time (and will) made it not happen.
That 0.26 was supposed to be a short-cycle released didn't help. I see
0.26 mostly has a bug fix release and/or finishing features that were
incomplete in 0.25