On Sun, Feb 24, 2013 at 07:11:22PM +0100, Reinhard Tartler wrote:
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -547,4 +547,99 @@ why the expected result changed.
>
> +@anchor{Release process}
> +@section Release process
> +
> +Libav maintains a set of @strong{release branches}, which are the
> +recommended deliverable for system integrators and distributors (such as
> +Linux distributions, etc.). At irregular times, a @strong{release
> +manager} prepares, tests and publishes tarballs at the
on the
> +@enumerate
> +@item
> + @strong{Major releases} are cut from the @strong{Libav}
> + @code{master} branch. They may included the latest and greatest
include_
> + features and functionality. However, the resulting shared libraries
> + must not break applications that have been compiled against previous
> + versions of @strong{Libav} in any case!
So no API breaks, ever?
> +@enumerate
> +@item
> + Fixes a security issue, preferably identified by an @strong{CVE
a CVE
> +@item
> + Retains both source-code and binary compatibility with previous
source and binary
> +All Libav developers are welcomed to nominate commits that they push to
are welcome
> +@code{master} by mailing the @strong{libav-stable} mailing list. The
> +easiest way to do so is to include @code{CC: libav-stable@@libav.org} in
> +the commit.
in the commit message
> +@item
> + File a release tracking bug in @url{http://bugzilla.libav.org}. Make
I'd use "Bugzilla" as link name instead of the full URL.
> +@item
> + Announce the intend to do a release to the mailing list.
intenT, on the
> +@item
> + Reassign there unresolved blocking bugs from previous release
> + tracking bugs to the new bug.
s/there//
> +@item
> + Prepare the release tarballs in @code{xz} and @code{gz}
> + formats. Also include files containing @code{md5} and @code{sha1}
> + checksums.
It's not clear where the checksums should be included.
Prepare ... formats as well as files containing ...
> +@item
> + Publish the tarballs at @url{http://libav.org/releases}. Create an
anD, stray double space
> +@item
> + Build the tarballs with the windows binaries, and publish them at
> + @url{http://win32.libav.org/releases}.
Windows
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
