[FFmpeg-devel] Backport keywords

Michael Niedermayer michaelni at gmx.at
Thu Feb 12 21:06:54 CET 2015

Hi all

ubitux pushed me into thinking about $subj, so heres some suggestions

Commits which are security relevant must be backported
Other (important) bugfixes can be backported as well, if someone wants
to do the work.
Authors/Maintainers/Release maintainers should backport these commits
OR should add a "Backport-to:" Keyword with a list of releases to
which backporting is needed
(theres no need to add that keyword if one intends to do the backport
 by oneself)
Backport-to: 2.5, 2.4
Backport-to: 2.5-2.4
Backport-to: *-2.4
Backport-to: *

Listing the versions makes it simpler to thouse who do the actual

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing more to fear from them, then he is always stirring up
some war or other, in order that the people may require a leader. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150212/d7da1170/attachment.asc>

More information about the ffmpeg-devel mailing list