[gst-devel] upcoming core and base releases

Wim Taymans wim at fluendo.com
Wed Feb 21 12:40:57 CET 2007


On Wed, 2007-02-21 at 12:26 +0100, Thomas Vander Stichele wrote:
> Hi Team !
> 
> We want to do core and base releases so distros can work on the codec
> integration stuff.
> 
> However, it would seem that there have been commits to core adding API
> and functionality that some people have doubts about.
> 
> We used to have an unwritten policy of not commiting stuff to CVS that
> is not ready yet to go in the next release.  This policy allows us to
> actually do releases when we need to (security fixes, important
> features, ...)
> 
> Destabilizing work, work with new unfixed API, .... should all be done
> on a branch.
> 
> Is there a reason to move away from that policy, or should we stick to
> it ?
> 
> If we stick to it, can we discuss what these changes are (I don't know
> much about them) that we do not consider ready for a release, and either
> disable them or move them to a branch ?

I want to back out two new messages that were added:

GST_MESSAGE_LOST_PREROLL
GST_MESSAGE_PREROLLED

Along with the constructors and parse methods, I'm not happy with them
yet. The other message, the queries and events are ok.

Wim

> 
> Let me know what you think.  I want to push for releases for next week.
> 
> Thanks
> Thomas
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> 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