Re: [FYI] critical bug in EMI2 module
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
> Haven't someone branch the code on 1.2.0 ? > If so (I hope so :P), the fixes (not the new features) should have > been commited on HEAD AND on 1.2.0 branch, and now we'll just have > to tag a 1.2.1 and release it. yeah, I branched it for 1.2.0. Fixes have currently been commited to HEAD. Ok, so I have to commit the bug fixes to the 1.2.0 branch, tag the branch as 1.2.1 and release as a stable updated release. > we should have tagged 1.2.0 with 1.3.0 too, so now we could release > 1.3.1 with the new features (if any). Why is that?! When we release with new features it's HEAD is anyway tagged for a new version number. > Don't just release HEAD as 1.2.1... if 1.2 is stable, it should only > include fixes. yep, +1 from. There are at least 2 new features since the fixes and I don't want to release things declared as "stable" unless we have enough time passed to let people try things out. Stipe [email protected] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [email protected] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are