Closed sesuncedu closed 7 years ago
It would be useful to have coordination among releases - it's theoretically possible that important bug fixes require a patch release in either library. Of course, a big bug in the OWL API might mean it's best to update JFact dependencies, so a new release would be helpful - but it wouldn't work the other way around, so at times the patch version will likely be off.
Regarding when things are tested, I've checked that JFact and the other notorious reasoners were working well, or only required few changes to do so, before releasing version 4 - but that has been the first major release, with significant API changes, in JFact's lifespan, so "always" here is a bit of a weasel word :-P
With the current owlcs style of using exact version numbers is kept up, releasing a JFact 4.01 etc when a new owlapi is released (possibly with only dependencies updated, possibly with bug fixes) might be useful. Since Jfact has a parallel 3-way split this may reduce (or increase) confusion.
It could also make sense to have dependencies be for version ranges covering patch releases (JFact is always tested before an owlapi release is pushed, right)?