| Subject | Re: [firebird-support] Re: Confused about Firebird releases |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-12-28T05:31:31Z |
At 03:16 PM 28/12/2008, Adam wrote:
This discussion has become off-topic for firebird-support, but for once I'm going to let it roll. There are more than 6000 of you subscribed to this list. All but ~ 200 of you are happily accustomed to downloading the exact Firebird binary you want with no thought about what it's costing *someone* to provide it. When it comes to field-testing and reporting back you are a lazy bunch. We are lucky to get half a dozen of you contributing to this and it tends to be the same half-dozen.
Adam and others - I am *really* curious (actually, read that as "anxious") to know where you think the money comes from to fund the three full-time and several part-time codeworkers who deliver Firebird to you.
Right now, it is REALLY important to ALL OF US, including you non-payers, to hear your theories about a) where the money comes from, b) how long you think it is going to last and c) what you're going to do when it runs out completely.
Helen
>It took us 12 months to trace, remove or rewrite code that the 2.x orYou might be surprised. Each patch release takes developer resources, build resources (multi-platform, multi-architecture), QA resources, documentation resources, web resources. So - try not to trivialise what it takes to get Firebird releases and patch releases out there to keep you all safe and happy.
>2.1 engine finds ambiguous, or chooses a plan less optimal than the
>1.5 series. Granted this was not a goal we gave special focus to, but
>it is only last month we could actually claim full support for 2.1.x.
>
>We were able to move through the point releases of 1.5 with targeted
>testing within a week of release and with no code changes from our
>side. It takes a lot more effort to migrate to a new major version,
>arrange for acceptance tests and then perform upgrades for hundreds of
>customers.
>
>I doubt that releasing security fixes for old versions significantly
>delays new versions of Firebird. I imagine it would be the same
>changes made in different branches.
This discussion has become off-topic for firebird-support, but for once I'm going to let it roll. There are more than 6000 of you subscribed to this list. All but ~ 200 of you are happily accustomed to downloading the exact Firebird binary you want with no thought about what it's costing *someone* to provide it. When it comes to field-testing and reporting back you are a lazy bunch. We are lucky to get half a dozen of you contributing to this and it tends to be the same half-dozen.
Adam and others - I am *really* curious (actually, read that as "anxious") to know where you think the money comes from to fund the three full-time and several part-time codeworkers who deliver Firebird to you.
Right now, it is REALLY important to ALL OF US, including you non-payers, to hear your theories about a) where the money comes from, b) how long you think it is going to last and c) what you're going to do when it runs out completely.
Helen