On 04/16/2011 10:57 AM, Reinhard Tartler wrote: > Hi, > > while still travelling but having lurked from time to time on IRC, I > note that some downstreams express some interest in libav 'snapshots'. > In this context, I'd like to introduce and clarify a nomenclature which > I think matches the workflow that Libav uses.
Nice =) > Releases: The Libav projects blesses deliverables in form of source code > archives that are intended to be used by users and other downstream to > use directly or have their application linked against them. > > Starting with 0.6.2, these releases are accompanied by binary archives > for the win32 platform. Do we want and have the ressources to a) > continue this and b) extend this to include .deb and .rpm packages? for win32 we have actually 3 experimental flavours with a fourth one coming up later. I'd like to have more feedback since I'm trying to work closely with mingw-w64 in order to fix possible toolchain bugs and improve the overall experience. > I'd like to publish the text above on our website somewhere, so comments > on the text itself and the location (e.g., the download page? new page?) > are more than welcome. Having said this, I hereby nominate revision > 14622ef0 as 0.7b1, i.e., the first beta release of the 0.7 release > series. I have verified that this version compiles fine with latest > mplayer svn. [1] I'd have a subsection of About or a new Release section for it. > After the tarball has been published (I currently lack write access to > the release directory) and the revision is tagged, we can consider > improving the version string produced by the script version.sh. > > A word on release frequencies: a number of downstreams have expressed an > interest in more and faster releases. For this reason, I propose a > frequency of ~8-12 weeks for beta releases and 2 new 'release series' a > year, which I think is manageable given the current resources that we > have. Seems good for me (donning the Gentoo hat). lu -- Luca Barbato Gentoo/linux http://dev.gentoo.org/~lu_zero _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
