[REQ] commiting bugfixes to stable 1.4 branch
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | The Kannel Group |
| Message-ID | <[email protected]> |
Hi list,
for all developers with cvs access, please obey to commit bugfixes that are
logically fixing issues in the current 1.4.0 stable release to _both_ branches:
HEAD and stable_1_4_0
We will use the stable_1_4_0 branch to release an updated stable release called
1.4.1 after some fixes have been applied.
Feature adds and things that are new should go into HEAD. Fully experimental
code should go into an own branch, as Alex did this for the new autoconf stuff.
Is this policy ok for all? I just want to prevent to mess up the HEAD branch,
when releasing 1.4.1 (stable) and have code inside that is "yet not fully
tested" or something similar.
I just commited the gwli/[conn|http|charset].c commits to the stable_1_4_0 branch.
Comments please?! ;)
Stipe
mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------