Dear Developers! My team has been developing an ERP system using Firebird RDBMS for almost 18 years. After Interbase times, we moved to Firebird from 1.0 to 2.5 during this time. We've been working for years on the transition to 3.0 and dialect 3, this year maybe the time will come for us to move on. Hundreds of customers, thousands of databases, very complex business logic, in many places even retaining / using data recorded 18-20 years ago. If the migration succeeds, we will be much closer to 4.0 and the much-anticipated possibility of replication, which we are also testing in parallel anyway.
All of this, of course, required and still requires your work, to put a reliable database manager under us. I appreciate this work and would like to thank you again! Reading the developer's list these days I found the following that I suggest you for consideration: github lists 776 open bugs (is: issue is: open label: "type: bug"), these should be clarified first. Sure, there are plenty of them that can only be tied to an unsupported version and can therefore be closed, ones that the reporter may no longer consider important, and ones that in turn cause a serious problem and need to be fixed. We know that the exciting challenge in a developer's life is usually to develop new features, rethink and refine existing ones. But bugs also need to be fixed, and sometimes it's worth allocating more resources to them than putting new things into the code. >From my side, I will provide resources in the coming weeks for colleagues to >review and either close or confirm what we have announced over the years if >they still cover a real problem. I encourage everyone who has recorded a ticket in recent years to do so. Perhaps this is the most what we can do to help the core team's work. In Berlin, we heard from Dmitry Yemanow that after 4.0 the goal should be to release a version every year. If this is still the goal, it might be simplier to design the first version so that most of the improvements would be bug fixes. Maybe it's easier to "stop" with the fixes and say it's enough now, it's time for versioning than to do the same when new features / deap changes are added in large numbers. I'm sure because of replication, 4.0 will be used by a lot of people, including developers of programs that are rooted long ago and carry a lot of compromises like us. I'm also sure that's why a lot of problems will come up in 4.0, which is already there in 3.0, but it still hasn't come up because a lot of people haven't switched to it yet. Such systems would benefit greatly if they could even switch to 5.0 after fixing these and previous bugs, but let's say using the old API if they only have the option. Finally, I would like to thank everyone once again for their work and for delivering us Firebird to such a standard and quality for two decades! András OMACHT Development director Libra Software Ltd. Hungary __________ Information from ESET Mail Security, version of virus signature database 23348 (20210524) __________ The message was checked by ESET Mail Security. http://www.eset.com
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
