[gst-devel] Required GLib version policy

Stefan Kost ensonic at hora-obscura.de
Wed Feb 25 16:22:40 CET 2009


Tim-Philipp Müller schrieb:
> Hi,
>
> I think we should try to bump our GLib requirements more often. Slowly
> and conservatively, but regularly.
>
> To this effect I propose some sort of informal GLib version policy,
> something like:
>
>  - whenever we release core/base, we look into
>    bumping the GLib requirement for core/base
>    (ie. right *after* the core/base release, not
>    for the release itself)
>
>  - we then look at all (stable) GLib 2.N.1 releases
>    that are older than ~12 months, and pick the
>    highest N. That's our new GLIB_REQ then.
>   
I like it. We miss all kind of new api already, e.g. g_sequence would be
nice to being able to use. I think a regular scheme has the benefit that
it takes place. Like doing regular releases. If there is a know problem
ith a new glib, then people will have issues with that one anyway,
regardless if we requeire it or not.

Stefan

> The overall effect would be that when we release the next core/base the
> required GLib version would be at least around 15-18 months old, which
> seems fair to me (and what I think emerged as acceptable consensus the
> last time we debated this issue on the mailing list).
>
> So:
>
>  - GLib 2.N.1 would be at least 12 months old
>    *when we bump the requirement* (at this point
>    only affecting GStreamer hackers)
>
>  - a core/base with this new requirement would
>    be done ca. 3 months later, so at the time
>    this new requirement hits GStreamer consumers
>    and distributors the GLib version required
>    would be at least 15 months old
>
>  - any GLib 2.N.x series will typically be
>    maintained and in use for 6-9 months (random
>    info on the side)
>
> Thoughts? Sound good?
>
> Cheers
>  -Tim
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>   





More information about the gstreamer-devel mailing list