On 22 March 2013 13:04, Vadim Zeitlin <[email protected]> wrote: > > I'll try to do this properly, i.e. add the unit tests exposing the bugs > these commits fix, but this will take me some time and might not happen > before the next week so for now I'd like to ask to either delay SOCI 3.2 a > little bit or commit (or let me commit) the changes below without the > tests as without them current Firebird is simply unusable for us and > anybody else either re-using the same statement more than once or reading > any floating point numbers from the database.
Vadim, I'd prefer to complete the release this weekend for two reasons: 1. I may be too busy after this weekend for another month 2. There is a client who asked if it is possible to release 3.2.0 soon, and it's already delayed. I assume that you have tested the fixes and you've got best picture what's the state of the backend. If you say we can release without the tests added, just with the fixes, let's do so. I see no problem with adding the tests after release (in develop branch), if we collect some more fixes, before we are done with SOCI 4.0.0, we can always roll out 3.3.0. Are you OK with releasing your fixes but without tests in 3.2.0? If you want to either add them together or not at all, then I will adjust and postpone release. Best regards. -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
