A 2.x release doesn't require a whole lot of additional work, although there is usually a target date and an effort to kill as many bugs as possible beforehand.
Bug-fix releases (e.g., 2.3.x) are made periodically and appropriate patches are "cherry-picked" from the development tree to the stable tree. These are usually for the purpose of maintaining binary compatibility. At some point, there will be an Open Babel v3 push, and the API will break. At that point, every effort will be made to make a more stable binary interface which doesn't break with every release. But I'm less convinced this is an important goal. I agree with Craig that the versioning scheme (2.3.x) will not change anytime soon, particularly because Linux and BSD and similar distributions *hate* date-based versioning. Heck, many of them don't like it if I call something 2.4.0b1, preferring 2.3.90. -Geoff ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
