Hi!
We previously decided that we does not need to maintain API
compatibility within mistakes done in alpha/beta versions.
So interfaces does not need to be versioned between unstable releases.
So it does not make sense to me to have more than one "version:" between
official releases.
We curren
On 2/17/21 6:33 PM, Adriano dos Santos Fernandes wrote:
Hi!
We previously decided that we does not need to maintain API
compatibility within mistakes done in alpha/beta versions.
So interfaces does not need to be versioned between unstable releases.
So it does not make sense to me to have more
[
http://tracker.firebirdsql.org/browse/CORE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Rotteveel reopened CORE-6487:
--
I'm reopening the issue as it also needs to be backported.
> FETCH ABSOLUTE and RELATIVE beyond bo
Hi!
We previously decided that we does not need to maintain API
compatibility within mistakes done in alpha/beta versions.
So interfaces does not need to be versioned between unstable releases.
Well, you may not need to maintain API compatibility, but there does
need to be a clear and systemati
17.02.2021 18:06, Tony Whyman wrote:
For Firebird 4 RC1, the version number gets reset to 4
Only as a bugfix for wrong Pascal files generation.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 2/17/21 8:15 PM, Dimitry Sibiryakov wrote:
17.02.2021 18:06, Tony Whyman wrote:
For Firebird 4 RC1, the version number gets reset to 4
Only as a bugfix for wrong Pascal files generation.
Just to be explicit - later you may rely on a fact that next version
will be >4.
Firebird-Deve