On Fri, Sep 7, 2012 at 2:13 AM, Anton Khirnov <an...@khirnov.net> wrote: > > On Fri, 07 Sep 2012 00:34:14 +0200, Diego Biurrun <di...@biurrun.de> wrote: >> So, could we make a new release soon? I know there are a few issues here >> and there, but nothing serious should be blocking it. gstreamer is about >> to release 1.0, they would benefit from a libav release. >> >> Maybe we can at least roll a 0.9-alpha tarball and promise not to make >> any more API changes until 0.9 proper. Thoughts? >> > > How about this: > > 1) fix doxygen (in some way that would be acceptable to everybody) > 2) put out a pre-release (call it alpha, beta or whatever) > 3) nicely ask people to not push anything big and likely to cause > regressions until the release > 4) do some cleanup > -- go over bugzilla and fix some outstanding bugs. At least I have some > lavfi stuff on my list, there's probably more low-hanging fruit to be > found. > -- everybody could look at his unarchived patches in patchwork and either > mark them as resolved or ping them. > 5) release 0.9 > 6) ??? > 7) profit >
Please excuse me if I'm talking out of turn here: In general I agree, except for #3 -- I always assumed that doing a "code freeze" was not appropriate for the way we all like to work on libav. Maybe we should cut an 0.9 branch (properly this time so FATE shows we are working on HEAD instead of 0.8)? -- Sean McG. _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
