On 15/08/12 08:20, Holger Knublauch wrote:
On 8/13/2012 5:20, Andy Seaborne wrote:
On 12/08/12 02:46, Holger Knublauch wrote:
...
but we and our customers have an unknown number of queries in
production
...
TQ gets Jena for free.
Yes and this is greatly appreciated. You guys are doing an amazing job.
We have built quite an empire on top of that. You will understand why I
am especially sensitive to surprising changes to the foundation of our
software stack. Please accept my apologies if I sounded too frustrated.
What would help is if TQ tested against the nightly snapshot builds
especially just before a release. The project makes available
development builds at all times so we can deal with such issues early,
before a release.
This would be good, but would be limited to cases in which the Jena API
itself remains stable. Usually there are always some API changes that
won't even make our stuff compile without changes. This plus the
overhead of setting up the infrastructure has prevented us from doing
continuous testing.
The API changes very rarely, with deprecation cycles usually over
several versions.
In the past, TQ have called into internal code - surely, knowing in
advance when that changes is important to maintaining your software.
Even then, such events are rare.
It's TopQuadrant's choice - test early or test late and risk exposure to
unintentional changes made for the better that have been other people
may now depend on.
Andy
