Annoucements about Firebird oficial releases.
Dmitry Yemanov just confirmed that we can expect Firebird Release Candidate 2 to be released this month (January/16). The source code should be tagged in the next 2 weeks, and after that, it is just a matter of the documentation team finishing the release notes.
(9 votes, average: 4.78 out of 5)
Loading...Firebird Project is happy to announce general availability of Firebird 2.5.5 — the latest minor release in the Firebird 2.5 series.
This sub-release introduces several bug fixes and a few improvements, please refer to the Release Notes for the full list of changes. Binary kits for Windows, Linux and Mac OS X on both 32-bit and 64-bit platforms are immediately available for download.
(3 votes, average: 5.00 out of 5)Loading...Firebird Project announces the first Release Candidate of Firebird 3.0, the next major version of the Firebird relational database, which is now available for testing.
This Release Candidate demonstrates the complete set of features and improvements developed for the new release. Release Candidates are generally considered stable enough and may be recommended for testing in “almost-production” environments. Please report about any found bugs to the bugtracker.
Please read the Release Notes carefully before installing and testing this Release Candidate.
Download page:
http://www.firebirdsql.org/en/firebird-3-0-0-rc1/
Release Notes:
http://web.firebirdsql.org/download/prerelease/rlsnotes/Firebird-3.0.0_RC1-ReleaseNotes.pdf
—
Dmitry Yemanov
(6 votes, average: 5.00 out of 5)Loading...Firebird 3 Release Candidate 1 is now tagged at Sourceforge. Next steps are: run the QA tests, prepare docs, and release it for testing.
(11 votes, average: 4.73 out of 5)Loading...This version will make the build reproducible.
The reproducible builds initiative aims to enable anyone to reproduce bit by bit identical binary packages from a given source, thus enabling anyone to independently verify that a binary matches the source code from which it was said it was derived. For example, this allow the users of Debian to rebuild packages and obtain exactly identical packages to the ones provided by the Debian repositories.
Prune tool sets the creation stamp in the database header to a fixed value (taken from the last changelog stanza) and
prunes unused space on index/data pages of shipped databases
(1 votes, average: 5.00 out of 5)Loading...At the 12th Firebird Developers Day, I talked about Using Firebird in high latency networks (aka. internet). Below are two slides from my presentation, where you can see the improvements in Firebird 3 wire protocol, compared to FB 2.5 and to MySQL.
Enjoy!
Obs: Left axis values are expressed in seconds. Test server was hosted in Amazon (USA) and client accessing it was located in Brazil. Ping reported latency of 219ms. The smaller the bar, the better.
Above graph shows the result of fetching 10.000 records from a real table used to store customers data. Red bars represents records with all the fields filled (ie: there was no fields containing nulls) and blue bars represents fetching records where some of the fields were nulls. Tests where done with and without compression.
The same table used in previous graph was created in MySQL InnoDB (same data). Blue bars means that wire compression was disabled, and red has compression enabled. Left side graphs has all fields filled (ie. there wasn’t null fields) and in right side graphs, some records has some null fields.
As you see, FB 3 won 😉
I should mention that there was no blob fields in the table, and this makes a lot of difference. Fetching non-null blobs makes the fetch slower in Firebird (more roundtrips are needed).
PS: The improvements in the FB 3 wire protocol were sponsored by donations collected in the 9th edition of FDD conference, and were implemented by Dmitry Yemanov. Compression was implemented by Alex Peshkov.
(24 votes, average: 4.67 out of 5)Loading...Firebird Project announces the second Beta release of Firebird 3.0, the next major version of the Firebird relational database, which is now available for testing.
This Beta release demonstrates the features and improvements currently under development by the Firebird development team. Our users are appreciated giving it a try and providing feedback to the development mailing list. Apparent bugs can be reported directly to the bugtracker.
Beta releases are not encouraged for production usage or any other goals that require a stable system. They are, however, recommended for those users who want to help in identifying issues and bottlenecks thus allowing to progress faster through the Beta/RC stages towards the final release.
Please read the Release Notes carefully before installing and testing this Beta release.
(8 votes, average: 5.00 out of 5)Loading...Firebird 3.0 Revision 61479 was uploaded to Debian/experimental.
Now you can install on Ubuntu 14.04 LTS or latest release 15.04 (Vivid) from firebird3.0 ppa
Changes:
* Remove extra ‘;a=summary’ from the Vcs-Browser URL
* -server.postinst: s/LOGDIR/LOG_DIR/ spelling mistake (This solved an package install issue – basically it stopped the installation process)
* Imported Upstream subversion snapshot r61579
* fix populating -dev with include/firebird/* content
(1 votes, average: 5.00 out of 5)Loading...Firebird 3.0 Revision 61579 uploaded in into Debian experimental with a few
Changes:
* Remove extra ‘;a=summary’ from the Vcs-Browser URL
* -server.postinst: s/LOGDIR/LOG_DIR/ spelling mistake
* Imported Upstream subversion snapshot r61579
* fix populating -dev with include/firebird/* content
(1 votes, average: 5.00 out of 5)Loading...Firebird 2.5.4 is currently the latest stable release. Detailed information about new features and improvements can be found in the release notes.
(5 votes, average: 5.00 out of 5)Loading...