Hi, > I started a small discussion with Oli about our branch management but it > is perhaps no good idea to make it more complicated. The idea was to > introduce feature and minor release branches on the 0.9.2 branch. The > problem is that this is perhaps to complicated for the most people. > > We have actually a fully stable 0.9.2 which is ready for release. So the > question was/is what to do? Release 0.9.2.3. Add utf8 support and > immediately release 0.9.2.4 or only release the stuff as a patch. I > would prefer the immediate 0.9.2.3 release and after some days a 0.9.2.4 > release but perhaps this is too confusing?
well, we agreed only to include bug fixes to the stable branch. I plead guilty of breaking this rule by adding some modifications to the core modules, but these are all passive unless explicitly used by the caller. In terms of user transparency I think it is not very useful to split yet another branch off OpenCA (0.9.2 release, 0.9.2 experimental and 0.9.3). The first reason is that this would require another level of versioning numbers (five is too much, I think). In addition we would have to maintain another branch - not good. I'd suggest we keep the two existing branches. Work on the 0.9.2 branch should remain very conservative - this could mean that all new additions are by default deactivated and must be explicitly activated in the configuration. In addition, of course, all additions should be tested very carefully before including them in 0.9.2. I don't know if this is feasible with the utf-8 patch, though. Martin ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ OpenCA-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openca-devel
