On 14.08.2017 18:08, Slavomir Skopalik wrote:
May be we can start new topic about bug fixing and release strategy.
Two examples:
1. Database corruption
(http://tracker.firebirdsql.org/browse/CORE-5392) that I was reported
06/Nov/16, release contain this fix was available 22-Mar-2017
2. Server crash (http://tracker.firebirdsql.org/browse/CORE-5562) that
was reported 07/Jun/17 will be released Q3-Q4 2017
Because of 1 we have to downgrade to 2.5 and till now, no stable
release available.
BTW - why not use snapshots? Currently they pass same tests control as
releases. Review tests result and if nothing critical present - fill
free to work with snapshot. For stable releases snapshots are pretty stable.
Now we using FB2.5 for production and development. For testing we are
using FB3.
Back to original topic, I don't believe that is right time to drop
support for FB2.5.
Nobody suggest that. But please distinguish between support and new
features. Developing new features limited with old version is not good idea.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
