From: Guenter B. <bar...@we...> - 2003-02-12 13:01:44
|
hallo miguel, On 02/06, Miguel Freitas wrote: > > > nevertheless i must say i disagree with Guenter. branching releases may > > > work fine when you have a big team of developers doing both bugfixes and > > > improvements, like mozilla. people will naturaly work on the branch they > > > are interested and you make both teams happy. > > > > actually i do believe xine needs a team of release managers and a team > > of head developers and i think the xine project is big enough to have > > both (of course it is ok if people work on both teams). > > > oh, i'm sure the project is big enough to have much more than that. i > miss some beta testers, qa team, documentation maintainers, graphics > designers... my point is that while we do not have all these people > working on xine, some processes will simply not work well, like the > "stable cvs branch" idea 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 > > one thing that > > needs to be done is finally getting that trouble ticket system to > > production use so patches and bugs can really be tracked - at the moment > > far too many bugs get lost unfixed (i keep finding old bugs that i know > > have been reported and forgot more than once). once we have these two > > things installed (release branches and a tracking system) we can really > > think about working towards a 1.0 release. > > > tracking system helps, but it doesn't do magic. people sometimes reports > bugs on xine-devel that nobody wants to look. that's fine, this is a > collaborative effort and we all work for free, we have no obligation to > answer every email. > > just note that having a tracking system does not mean that > issues/bugs/patches will be taken care by developers. it just make the > job easier for developers who are already tracking these things. it will also encourage developers who didn't care about bug reports and patches until now to start doing that - personally i would "care" about a lot more patches and bug reports if there was a way to store them easily somewhere where i can be sure they will not get lost and are easy to find again > > i'd like to make life as easy as possible for developers who work on > > bringing xine forward - those people need freedom and should not get > > distracted any more than necessary - big changes are a lot of work and > > often difficult - that's why i'd like to keep away the burden of taking > > care of cvs branching from them. > > are you kidding, aren't you? > you mean that a developer which knows xine well enough to make a big > change doesn't know how to use cvs branches?? 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. > > release managers who are mostly tracking and applying patches, and > > who's job it is to do tagging and merging wouldn't have much extra work > > with managing those branches, in fact, i believe it would make their > > live much easier. > > are you planning to hire some people? ;-) from what money should i pay them? cheers, guenter -- "The two most common things in the universe are hydrogen and stupidity." |