Re: xine development process [was: xine and post plugin segfault.]

Hi Guenter,

On Wed, 2003-02-12 at 07:48, Guenter Bartsch wrote:
> humm - branching releases should make life easier for those making
> releases and imho is a requirement for having a 1.0 some day (can you
> really imagine releasing a 1.0 tarball from cvs head one day?) and as we
> have a release maintainer at the moment i'm sure we'll find people to
> maintain this process


Actually i see no problem in releasing 1.0 tarball from cvs HEAD.

That's just a matter of commiting only stable stuff and bugfixes to cvs
head. 

for example, we use a cvs repository in my work for a production
software (think of an application for inspection of oil & gas pipelines
- it really can't fail), the most stable is always available from cvs
head or last tag that passed burn-in tests. new drivers and fixes can be
commited there but experimental changes (those that can introduce
breakage) belong to separated branches.

I really want to have the cvs head stable as possible and i've always
being working on that direction. you know that i have daily rpm builds
from cvs and i want them to be useable. this way i can commit fixes to
cvs and users are able to test them on next day.


> sorry, you must have completely misunderstood me here. i did not say
> that i think developers don't know how to use branches, i said that i'd
> like to keep away the burden of taking care of cvs branching from them.


Sorry, i still disagree. branching is quite easy, just a single cvs
command. if anybody wants to avoid the "burden of cvs branching", ask me
and i would create the branch for him ;-)

besides, having a branch to experimental/buggy code is the total freedom
for the developer... nobody will flame you because broken stuff, nobody
will play with your code unless they are willing to...
 
See last Daniel's post, i completely agree with him.

regards,

Miguel




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf