Firebird related news
For Laravel 5.2 support, please look at the 5.2-sup branch in the laravel-firebird repository
https://github.com/jacquestvanzuydam/laravel-firebird/tree/5.2-sup
For Laravel 5.2 support use:
composer require jacquestvanzuydam/laravel-firebird:dev-5.2-sup
Thanks to CyCJIeHok for the changes for Laravel 5.2
Maximiliano Robaina wrote on Django-Firebird group : This is the proposed development roadmap for django-firebird
1. django-firebird for django 1.7 is in beta 1 status and available from pypi. I’m testing it on a real system, if all works ok, I would like promote this version to stable on April 1st (Friday)
2. django-firebird with support for django 1.8, release candidate 1 on 2016-04-08
3. django-firebird with support for django 1.9, release candidate 1 on 2016-04-22
Of course, this is a tentative schedule, I’ll appreciate any feedback.
Maxi Robaina announced on twitter : Django-firebird development is back the github version is in beta stage with django 1.7.x support by now. All tests passed ok
Support for django 1.8 LTS will begin next week and then django 1.9. I think it will be a version by week.
v1.7.0 beta 1 Changelog
Nikolay Samofatov announced he is using NBACKUP for physical replication of the databases and with patches for Firebird 4.x and 3.x
There is a medium difficulty task for a c++ programmer in current GSOC 2016
The Firebird driver for LibreOffice was started, and is mostly functional, in a previous GSoC, but it needs finishing and polishing. The main remaining issue is that the firebird data format embedded in the .odb file is endianess-dependent. The idea is to switch to Firebird’s “archive” format that is not.
Required skills / knowledge
C++, SQL, Reading other’s code, capacity to work autonomously.
Difficulty
medium
Potential mentors
Lionel Elie Mamane, IRC: schoinobates, mail: lionel AT mamane DOT lu
Firebird 4.0 Roadmap and Checklist.
Dimitry Yemanov announced :
The project repository was migrated to GitHub:
https://github.com/FirebirdSQL/firebird
Please wait a few days for things to settle down, we need to update some
infrastructure. SVN repository is still accessible, but new
contributions are expected to be provided as pull requests at GitHub.
When creating a GitHub account, we suggest to add your SourceForge’s
email (username@users.sourceforge.net) as a secondary one to associate
your past contributions with your account.
The Portuguese version of my new eBook, Guia de migração para o Firebird 3 (Migration guide to Firebird 3) was just released! The book has tips and explanations to make the life of anyone who wishes to move to Firebird 3 easier.
An English version of the guide will be available in the following weeks at Amazon, both in paperback and digital formats. This is my third book devoted to Firebird, and the first one to be published also in English.
Brazilians can buy the guide right now in the FireBase on-line store.
Carlos H. Cantu
Jaybird 2.2.10 has been released, see https://github.com/FirebirdSQL/jaybird/releases/tag/v2.2.10 … for details
Firebird Project will be moving its repositories to GitHub
Dimitry Yemanov wrote on Firebird-Devel list:
I’m asking present contributors to create accounts there. If anyone
(including past contributors) wants your past commits to be
automatically linked to your GitHub account and be shown in the
statistics, please report your account name in this thread, or make sure
that your *.users.sourceforge.net email is added as a secondary one at
GitHub.
For the moment there is already a github mirror for sourceforge firebird core
https://github.com/FirebirdSQL/core