RE: Patch submission and release policy (Was: [PATCH] problems with HTTPS and base support for per message billing)
Harrie Hazewinkel <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <7803896.1022691274@localhost> |
--On Wednesday, May 29, 2002 7:58 AM -0600 Alex Judd <[email protected]> wrote: > If we are to continue to use CVS as a bug fixing and feature adding > mechanism then we have to do this branching. > > Not doing so is going to mean that none of the 'live need to fix it now' > problems get fixed (or submitted back) as nobody can properly diff > against the bits they've fixed. I agree fully, that is why I said keep a main branch for development (unless very experimental) and make stable branches for the releases. After a release the branch should not need to have that many fixes. Unless we have not done our testing properly before testing. Harrie Internet Management Consulting mailto: [email protected] http://www.lisanza.net/