> Is every commit on master considered stable? How are releases validated > currently?
I don't think anyone is going to guarantee "every" commit. There are nightly CTest builds and Travis-CI will complain through GitHub if things break the test suite. There are many of us using master on a day-to-day basis. I think the technical term is "dogfooding." In addition to the test suite, there is an active push before release to squash as many bugs in the tracker as possible. > We use a git-flow style release strategy currently for our projects and would > need to follow the same strategy here for QA reasons (there's many great blog > articles on the benefits of doing this if you want to know more). I guess I'm curious about this. I suspect we are notorious for not making many releases and we should be better about more frequent versioning. The main problem has been that the most active maintainers (e.g., Noel and myself) have been pretty busy with other activities. If someone else would like to help out with version releases, I would personally be eternally grateful. :-) > We can (and will) do all this under our own namespace so there's no > confusion, but if the community would like to collaborate we think that would > be best. Mind if we (the community) ask a bit more about what you're planning on doing? Hope that helps, -Geoff ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
