Re: [xine-devel] life after 1.0

[Simon T. <si...@bi...>]

Miguel Freitas wrote:

> On Thu, 18 Nov 2004 16:19:39 +0100, Sylvain Skarsnik Colinet
> <sco...@gm...> wrote:
> 
>>I am not xine developer, but I think you can have a stable and test
>>branch. In stable branch you work on bugfix and progressiv improvment.
>>In test branch, you test external contribers patchs, test new
>>workaround, and big change, It can be a "play" branch :). You can
>>merge mature features in test branch to stable branch.
>>
>>You keep a quite stable version and a place to play and test new code :)
> 
> 
> yep. that's my idea, experimental patches (or anything that can
> possibly break xine somehow) should go to a separated branch.

This looks like a good plan, and I like Michael's suggestion of an 
automated patch script. Its clear from reading this list that there
is a small core of talented developers here who would be further
stretched if they are asked to review and manage several branches
at the same time. while I think you are correct in suggesting
it, might there be a way to form support teams to offload some
of these extra mangement tasks?

I would be concerned to see important core developers diverted
from the great work they do.

while I would like to contribute more to xine, I don't know how
I could be of assistence in this regard.

Simon