On 5 December 2012 20:10, Pawel Aleksander Fedorynski <[email protected]> wrote: > I have no idea. What are the rules for deciding that? It's a minor fix.
I have no idea. I don't think we have any rules. I was thinking about what MySQL version we support in 3.x and what we want to support in 4.x. The docs doesn't mention SOCI 3.x has been tested with anything bug 5.0.x but it mentions: "The SOCI MySQL backend should in principle work with every version of MySQL 3.x or newer.: http://soci.sourceforge.net/doc/backends/mysql.html If we want to issue bugfix release for SOCI 3.x then I need to list minor/non-intrusive and API-compatible fixes only. All other major changes would be released in SOCI 4.x. Alternatively, we don't bother with bugfix releases for SOCI 3.x and the current master will become SOCI 4.0.0. Then, we may decide to start bugfix branch and 4.0.1, 4.0.2, etc. releases. A few weeks ago, I proposed to follow the popular Git flow: http://sourceforge.net/mailarchive/message.php?msg_id=30107525 But, I'm still unsure, perhaps bugfix releases would be overkill for us. Equally, we may decide to work against master and from time to time we simply tag master's snapshot and issue a release. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
