[gst-devel] Doing new releases

[Christian Schaller]

On Wed, 2003-08-13 at 16:21, in7y118 at public.uni-hamburg.de wrote:
<SNIP>
> As a thought for the future I think it would be good if we adopted GNOME 
> standards for the 0.8 release. We should release this thing as stable and then 
> work for the next weeks/months on stabilizing that thing. Do some stable 
> releases and such. And after the new bugs don't become more and all important 
> stuff is fixed, we release one last stable release and branch off to 0.9 from 
> there. But don't branch off 0.9 with 0.8.0 or you end up with everyone 
> developing on HEAD only. 
Well this is where I think we all want to be, the reason we haven't gone
there yet is that it meant ABI stability which we where not ready to
commit to in the 0.6 timeframe.

Question is if we now feel confident enough to declare the ABI/API of
CVS head stable enough that we can be rather sure that 0.8, 1.0, 1.2 and
so on will be API stable between eachother.

> And don't close stable cvs for everyone. Two things 
> I've learned: Nobody likes feeling supervised when working on stable and nobody 
> likes doing work twice (aka backporting).

I think the closing of the stable CVS was the correct decision at the
time it was made, cause at the time before 0.6.0 we really needed to
clamp down on changes to get something ready/stable out. It could be
that we should have laxed the terms afterwards however, and I think for
our next stable series we probably should go for a much more open model
at least to see if it can work as well or better.

Christian