[gst-devel] API freeze
Thomas Vander Stichele
thomas at apestaart.org
Wed Oct 19 10:32:22 CEST 2005
Hey hey people,
only a little late, it's time to freeze the API of core for a month as
was announced in the summaries.
This means that from now on, no more API changes are allowed to be
commited to cvs. Instead, you should queue up your patches that change
API, and create bugzilla entries, and argument your changes.
Why is this important again ? It serves two purposes:
- element and application writers can enjoy this month of relative API
stability to try out this new API. If you were waiting for a good time
to do so, this month is it !
- it allows core hackers to review their current state of the core, do
code reviews, and see if they've got their bases covered and are happy
with what there is.
What happens after this freeze ?
A month from now, we will look if any API change requests are made. If
there are, we work through them as quickly as possible, and send out a
porting guide for those changes. We do this so we don't stab developers
in the back that we lured into our nest with our promise of one month of
stability. We also do this to have an exercise in pain management due
to not being able to break the API willy nilly.
What happens this week ?
If all goes according to plan, I will do a release tomorrow, and Wim
will start taking in twice his normal dose of nicotin as he bites his
right little pinky that was hovering over the Enter button before on a
cvs commit command line.
Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
Cause when I do
what I'm gonna do to you
You remember my name
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/
More information about the gstreamer-devel