On 15/08/12 08:20, Holger Knublauch wrote:
...
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
