| Subject | Re: [Firebird-general] About the "decrasing passion" of Firebird users. |
|---|---|
| Author | Alexandre Benson Smith |
| Post date | 2014-02-11T18:20:58Z |
Em 11/2/2014 14:26, Dmitry Yemanov escreveu:
We have SMP with CS and SC....
So, if during this alpha stage the development team find some really
serious problem with SMP on 3.0, we should wait for 4 ou 5 years until
it's fixed ? Or do you think that a re-schedule (realease a 2.6 or
anything you name it) with bug fixes, security fixes, new features, but
using the old SMP architecture, is not an option ?
I think we live on a dynamic world that anything could and should be
changed if it will be better.
So far CS fits me very well, and if I could (or need to) use the new
features of FB but stick with CS architecture I would go for it.
I think this is what the people are saying about incremental releases.
With the current release plan, or we get everything or we get nothing.
For me will be much more important to free Firebird from the 27 chars
restriction on object names, or a new wire protocol, than to have a new
SMP architecture. If one say that he needs 5 years to implement a new
SMP architecture, but 6 months to release a new version without the 27
char limit you could bet that I would choose the 6 months version.
And, in the background the longer tasks could be developed without
restricting the release of the new (not so major) versions.
me very well, but if I could put my hands on other minor features faster
I would get some benefits from it.
See you !
> 11.02.2014 18:34, Alexandre Benson Smith wrote:Really ???? I could bet my heart that it's to be shipped after 5.0 :)
>
>> We all know that FB 3 is a major architecture change.
> FB 3 was planned to appear after 2.0...
>> But, perhaps we could have FB 2.6 that could introduce (for example)That's the point... we could have minor versions with short release cycle.
>> Window Functions, Packages, etc.
> but in the meantime you had v2.1 with lots of features and v2.5 with
> another set of features.
> Delaying SMP further was not an option, sorry,No need to be sorry...
> thus no way for v2.6.
We have SMP with CS and SC....
So, if during this alpha stage the development team find some really
serious problem with SMP on 3.0, we should wait for 4 ou 5 years until
it's fixed ? Or do you think that a re-schedule (realease a 2.6 or
anything you name it) with bug fixes, security fixes, new features, but
using the old SMP architecture, is not an option ?
I think we live on a dynamic world that anything could and should be
changed if it will be better.
So far CS fits me very well, and if I could (or need to) use the new
features of FB but stick with CS architecture I would go for it.
I think this is what the people are saying about incremental releases.
With the current release plan, or we get everything or we get nothing.
For me will be much more important to free Firebird from the 27 chars
restriction on object names, or a new wire protocol, than to have a new
SMP architecture. If one say that he needs 5 years to implement a new
SMP architecture, but 6 months to release a new version without the 27
char limit you could bet that I would choose the 6 months version.
And, in the background the longer tasks could be developed without
restricting the release of the new (not so major) versions.
> DmitryAs I said before, FB 2.1 (yes I don't even use 2.5 in production) fits
me very well, but if I could put my hands on other minor features faster
I would get some benefits from it.
See you !