Hi, Dne 15.3.2013 12:53, Dmitry Yemanov napsal(a): > All, > > I see only two choices good enough for considering: > > a) Release 2.1.5.18497 and 2.5.2.26540 (suffixed with "Security Update > 1"), don't mark it as a separate release but replace the binaries with > the new version (like we did for the "bad" builds in the past). > > The question here is whether we need to publish the fixed v2.0.7 as > well. It's discontinued but present on our website home page. > > b) Defer the security patch till 2.1.6 and 2.5.3 but try releasing them > earlier than scheduled originally. IMO, this is easier to do with v2.5.3 > which is currently scheduled for Q2 and already has enough bugfixes than > for v2.1.6 that is expected to appear in late summer and still counts > only 11 bugfixes.
From QA perspective there is small difference between both. As we will have to run full QA on both versions at the same time (so expect it will take twice as much time as normally when we have only one at hand). However, B) means we will not run another round for 2.5.3 shortly after this one. If there are not enough fixes to roll out 2.1.6, then how about mixed scenario (2.5.3 + 2.1.5 with suffix)? regards Pavel ------------------------------------------------------------------------------ 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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
