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 stabl
On Wed, Oct 2, 2013 at 2:40 AM, Maciek Wójcikowski wrote:
> I'd like to bring the topic of release frequency of OpenBabel to the
> table. Since OB was migrated to the GitHub its development has speed up
> noticeably. Last release 2.3.2 was almost one year ago, and I think it's
> good time to discu
I'm happy to talk generally about release strategy. Usually development occurs
on the development version and stable fixes are back ported to 2.3.x branch (or
other stable version) close to the time of a release.
The reason for the slow release schedule from my perspective is that I just
submit
Hello,
I'd like to bring the topic of release frequency of OpenBabel to the table.
Since OB was migrated to the GitHub its development has speed up
noticeably. Last release 2.3.2 was almost one year ago, and I think it's
good time to discuss that matter. One major problem I've noticed is that
many
