> The only solution I'm seeing for this is testing. Maybe it would be > worthwhile to make ar release candidate before the actual release and > give a week for people willing to test the build to iron out all build > issues. > This would be ideal. I think I was even asking for it at some point a couple of years ago.
> Or they could participate in the prerelease testing which now is > done by devs only, AFAIK. I was participating in building/testing from svn before one of the releases in the past, spent quite a bit of time and effort only to discover that the release differed from what was in the svn snapshot so significantly that my testing was mostly useless. > Otherwise it's not really possible to guarantee no breakages when the > build system and library changes, but developers are not really using > all platforms. I know... I was just hoping the build system is stabilized on cmake at this point and there are not great changes in how plugins are compiled when going for a minor point update (2.3.0->2.3.1). Igor ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
