Merhaba,
Firebird 2009 Yol haritası açıklandı : http://www.firebirdsql.org/index.php?op ... 009&nosb=1
Genel itibarıyla notlar :
* Şu anda genel olarak 2.5 sürümünün gelişimi üzerinde devam ediliyor. Yılbaşından hemen sonra 2.5 Beta1 çıkacak. 2009'un ilk üç ayında RC1 ve ikinci üç ayında da final sürümü yayınlamayı planlıyorlar.
* 1.5 sürümünde bazı kritik hataları düzelten 1.5.6, 2009'un ilk üç ayında yayınlanacak. Bu yayınlanacak son 1.5 sürümü olacak. Destek devam edecek ancak yeni sürüm yayınlanmayacak.
* 2.0 serisi ve 2.1 serisinin güncellemeleri ve gelişmeleri devam edecek. 2009'un ilk üç ayında 2.0.5 ve 2.1.2 çıkacak. Sene sonuna doğru 2.0.6 ve 2.1.3 yayınlanacak.
* 2009'la birlikte 3.0 sürümünün geliştirilmesine başlanacak. İkinci üç ayda Alpha1 ve, üçüncü üç ayda da Beta1 sürümü yayınlanacak.
Yayınlanan Metnin Orjinali:
Firebird Roadmap 2009
The major Firebird version currently in development is v.2.5. Its feature set is being finalized at the moment in preparation for entering the Beta stage of development. The start of the Beta cycle will be accompanied by a "feature freeze" rule.
The v.2.5 cycle has presented more challenges than usual in the areas of debugging and testing, due to more significant technological rework in the multi-threading part than we expected. The effect has been some degree of slippage from the original schedule.
Once the v.2.5 Beta cycle is under way, we begin the development of the next major version - v.3.0. Some features for this release are already implemented by various developers in private source code trees, so these changes are awaiting mergers into the HEAD branch as soon as it is declared open for new development, planned for January. The addition of other features will follow, with appropriate discussions in the architecture and development mailing lists. Initial but still unstable snapshot builds for public review should appear soon after the development process has started.
February 2009 will be the fifth anniversary of the Firebird 1.5 release. At that point, it will be more than two years since Firebird 2.0 and almost a year since Firebird 2.1.
The next release from the 1.5.x branch (v.1.5.6) will be also the last one released by the project. It does not mean that this branch is no longer supported. Any subsequent releases, should they be needed, will be available from IBPhoenix on a commercial basis.
The Firebird Project's resources for development, QA and documentation will be dedicated to newer releases. More recent Firebird versions (namely: v.2.0.x and v.2.1.x) are still being maintained by the project and appropriate new bugfix releases are expected in 2009.
For more details about the anticipated releases, read on.
Release Details
The following blocks summarize the features and timeframes scheduled for each Firebird version series in the release plan for 2009. Click on the "Track Details" icons to see more details in the Firebird Issue Tracker.
Maintenance Releases
Series 1.5.x
* Critical (crash and database corruption related) bugfixes
* Security fixes
* Release v1.5.6 is scheduled for Q1 2009
* Further maintenance is going to be available commercially only
Series 2.0.x
* Critical and generic bugfixes
* Performance regression fixes
* Porting efforts
* v2.0.5 is in the RC stage now, final release is expected in Q1 2009
* v2.0.6 is scheduled for Q4 2009
Series 2.1.x
* All kinds of bugfixes and performance improvements
* Porting efforts
* v2.1.2 enters the RC stage after the Christmas holidays,
final release is also expected in Q1 2009
* v2.1.3 is scheduled for Q3 2009
New Development
Version 2.5
Goals and features:
* Updated codebase with full multi-threading support
* Thread-safe core engine and client / embedded libraries
* SuperClassic architecture (scalable multi-threaded mode with per-connection caches)
* Monitoring extensions
* ALTER VIEW statement; ALTER for computed fields
* Support for regular expressions in SQL
* Autonomous transactions
* User account management via SQL
* Extended EXECUTE STATEMENT command
* Queries against external databases
* Built-in tracing / audit facilities (still in development)
Schedule:
* Beta 1 is to be released after the Christmas holidays
* RC1 is scheduled for Q1 2009 as well
* We hope to see the final release going public in Q2 2009
* At least one maintenance release (v2.5.1) is expected in Q3-Q4 2009
Version 3.0
Goals and features:
* Revised architecture with flexible configuration
* Scalable (SMP/multi-core friendly) engine with the shared page cache
(SuperServer evolution)
* New authentication modes
* Metadata security enhancements (DDL permissions)
* Aggregated role permissions
* External (Java, C++, etc) stored procedures/triggers/functions
* User-defined PSQL functions
* Statement timeouts
* DDL triggers
* Monitoring extensions
* Optimizer improvements; more statistics collected and used
* Basic support for window functions
* Other (to be discussed and agreed on in the development lists)
Schedule:
* Source code tree is going to be opened for new development in January 2009
* Initial (unstable) public builds should be available in Q1 2009 as well
* Alpha 1 is expected in Q2 2009
* Beta 1 should follow in Q3 2009, with the hope of a first release candidate by the end of the year
Regards,
Dmitry Yemanov
Development Coordinator
December 2008