2010/9/13 Mateusz Loskot <[email protected]> > I have decided to go for simple approach: > SOCI_VERSION = MAJOR.MINOR.PATCH > SOCI_SOVERSION = MAJOR >
That's fine, I believe. Thinking of API/ABI versioning and given amount of changes that have > happened in SOCI, I've started to think that the upcoming > release should be numbered 4.0.0 rather than 3.1.0. > What about 3.5.0? There seems to be similar schemes in gcc, KDE and MySQL: 3.5.0 tells that there has been a leap forward, not necessarily backward-compatible with previous versions, and that it prepares a future version 4.0.0. Regards D
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
