Re: my role
Steven Armstrong <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
note: removed a bunch of cc's as you all get this mail through the list anyway. On 04/11/05 18:15, Wari Wahab wrote: > > I tell you what, I'll maintain the CVS, making sure that the tree don't > go astray. I will hopefully come up with some CVS guidelines, time > permitting, but for now I do hope the developers have some idea how one > is going about this. > > BTW, since the CVS branches are still young, we can always go back to > doing tags and just have HEAD. What say you? I am still waiting for > answers to: > > 1. Whether we should go with branches +1 > 2. Stick with old ways of doing things > 3. If we go branches: > 1. Should HEAD stay where it is > 2. Follow the last stable release > 3. Don't even have a DEVEL Personally I'ld have it like this: - development happens in HEAD - each release is tagged as a version, MAJOR_MINOR - if a bugfix is required for a release, create a branch and fix the bug there. If necessery merge the bugfix into HEAD. - the fixed branch is again tagged when released, MAJOR_MINOR_PATCH Just my 2 cents. I'll take whatever the gang agrees on ;-) cheers Steven ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click