On Thu, Oct 8, 2015 at 8:37 AM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > Hi > > ill make 2.8.1 soon from release/2.8 > if you want something backported push it to release/2.8 soon! > (or ask me to pull from your git tree, or if its trivial without > conflicts then the commit hash to cherry pick is fine too)
Can someone direct me to a doc on what should and should not be backported? Until now, I have (naively) not cared about all this release management stuff, coming from Arch anyway where the "latest is the greatest". Also, I assumed that whoever was pushing my patches would handle all such stuff, and anyway they would be a better judge of backporting than me. I think I should understand this for the time when I start exercising the commit privilege. In my simplistic view, although e.g not all undefined behaviors are exploitable, I still consider such things worthy of a backport as they don't introduce any new features, and fix bugs. Similarly, I consider all clean, simple bug fixes worthy of a backport. > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Everything should be made as simple as possible, but not simpler. > -- Albert Einstein > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
