[mythtv] ringbuffer.cpp

Gary Buhrmaster gary.buhrmaster at gmail.com
Mon Feb 24 17:50:02 UTC 2014


On Mon, Feb 24, 2014 at 4:41 PM, Jonas Arndt
<jonas.arndt at thearndtfamily.com> wrote:
....
> So that means that it will only show up in 0.28?

"It depends".  Pretty much *all* fixes are first applied to
the master development branch first, and then backported
only after they:

* Are complete/finished (not an in-progress fix)
  A number of patches start as in-progress work,
  so that that work is preserved, even if not complete.
* Are shown to work (based on feedback)
* Do not break something else (you might be
  surprised how often a fix breaks some other
  configuration; that is why a company like
  Microsoft can take years (or decades) to fix
  something, because the required change will
  break existing functionality)
* Do not require schema change which is only
  performed at a release boundary.
* Are backport-able with reasonable effort
  (some fixes are based on other fixes that
  make the work to backport excessive)
* They are important (not some trivial
   thing like a minor color change on a menu)
* A new release is not imminent
  (which may influence the amount of
  backporting work that a developer is
  willing to perform)

Even after all of those considerations, some packagers
will take some time (if ever) to provide new packages.
Some repackage daily, some a few times per release.

In this particular case, I would expect a backport,
but as with all such things, your mileage will vary.


More information about the mythtv-dev mailing list