On Fri, Aug 28, 2015 at 10:28 PM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > Hi all > > Its about 2 and a half month since 2.7 > if there are no objections then ill branch of release/2.8 from > some revission prior to the next API bump and will then make a 2.8 > release from that, after testing > if you want something in the release, push it prior to the bump OR > cherry pick it in release/2.8 afterwards but before the release is > made
Not really an objection, just a remark. I am working on colorizing the configure output. First patch is for warnings, and then I will try to take it from there. I don't think it would be good to have a half complete state on this for the release, though I consider this incremental work fine for master. Unless the release is delayed for other reasons, please hold off on applying this stuff to the release. > > ill pick some previously suggested name unless something specific is > preferred > release notes and changelog will be in the release as they are in git > at the time of release or if they are not in shape i will ommit them. > > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > It is what and why we do it that matters, not just one of them. > > _______________________________________________ > 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
