[gst-devel] 0.9 status

[Christian Fredrik Kalager Schaller]

Hi,
I would like us to do a release before we start on the split up process
as that it could quickly be a few weeks before the new modules are
functional and there have been a long time since our last 0.9 release.

So if there are no arguments against it I will roll tarballs of
gstreamer, gst-plugins-base and gst-plugins today and do a release of
each. In fact I would like to do this on a weekly basis for the 0.9
series so that we get updated code out there more quickly and widely.

Christian

On Wed, 2005-08-24 at 11:18 +0200, Thomas Vander Stichele wrote:
> Hi everyone,
> 
> An update on the state of 0.9
> 
> I still need to split up the gst-plugins module; I've attached a
> spreadsheet that lists all plugins + elements we have, their license,
> and their status.
> 
> I've decided I want to name the three modules -good, -ugly and -bad.
> Some names have been thrown around in the past, but none of them are
> short enough or convey nicely what they contain.  So unless people come
> up with a better suggestion, I'll stick with these.  (Since we can move
> around a complete CVS tree, we can still rename if we feel like it).
> 
> - good would contain code that lives up to our standards, is
> LGPL-licensed, adequately tested, ... It is comparable to -base, except
> that we decided that -base would only contain the elements it contains
> now.
> 
> - ugly would contain code that lives up to our standards, but is "ugly"
> because something prevents it from being in -good.  Most likely, this is
> a non-LGPL license or a known patent problem.  Stuff like mad,
> mpeg2dec, ... would live here.
> 
> - bad contains code that's not up to standard, not tested enough, just
> recently added and not yet fully working, ... Licensing/patent
> issues/... isn't really that important.  Code can be promoted from this
> module to either good or ugly, if the quality is improved.
> 
> The oo sheet attached lists where I would put each plugin; the ones that
> are undecided would probably default to bad until someone works on them.
> 
> After this is done, we can start doing a new release with these modules
> included.
> 
> I'd like to get this over with this week, so start flaming !
> 
> Thomas
> 
> Dave/Dina : future TV today ! - http://www.davedina.org/
> <-*- thomas (dot) apestaart (dot) org -*->
> To all the clumsy lovers who never seem to get it right
> <-*- thomas (at) apestaart (dot) org -*->
> URGent, best radio on the net - 24/7 ! - http://urgent.fm/
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel