Author: mariuz

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.

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

New version released with small fix : helper typo #63

https://rubygems.org/gems/activerecord-fb-adapter/versions/1.0.3

FDB Python driver for Firebird v1.5.1 is available for download.
https://pypi.python.org/pypi/fdb

Changelog for Version 1.5.1

• New connect() parameters: no_gc, no_db_triggers and no_linger.
• Direct support for with statement (PEP8) in Connection class.

Lazarus 1.6 has been released. This is the first release which uses FPC 3.0.

http://forum.lazarus.freepascal.org/index.php?topic=31575

Firebird/Java Engine Plug-in Status is : in development
Here is the repository :

https://github.com/asfernandes/fbjava

If you find any typos or mistakes, please report to firebird-docs

http://www.firebirdsql.org/en/news/firebird-2-5-language-reference-beta-1-released/

Firebird 3 is using new method to validate users on the server.
Direct upgrade of security database is therefore impossible.
Described procedure will let you keep the list of firebird 2.X users
and all related information (firstname, lastname, etc.) except
password – new passwords will be generated randomly. Pay attention
that SYSDBA user is not touched – i.e. it will remain as was after
execution of upgrade procedure. In the commands below replace
‘masterkey’ with actual SYSDBA password for appropriate (2.X/3.0)
firebird server.

In firebird 2.5 backup security database:

gbak -user sysdba -pas masterkey -b {host/path}security2.fdb security.fbk

In firebird 3 restore copy of 2.5 security database:

gbak -user sysdba -pas masterkey -c security.fbk {host/path}security2.5

And run users upgrade sql script:

isql -user sysdba -pas masterkey -i security_database.sql {host/path}security2.5

“security2.5” is a sample database name – you may use any other if you wish.

Upgrade Script will create users with new random passwords and type them to you.
It’s your responsibility to notify users about new passwords.