On 29/01/14 17:52, Michael Brunnbauer wrote:
Can I skip the time consuming step of producing a minimal example next time?
It took me maybe an hour.
The key issue here is resourcing.
It would take me a lot longer than one hour as I don't know your data or
indeed your query and it's history. You probably want me to spend my
time on the bits I can help with
I'm sure there is more information than the reduced test case. What
happens if the UNION branches were swapped? Why the LIMIT?
This may seem trivial but someone coming cold to a test case has to get
to grips with what's going on.
I've used "I" here - ultimately it comes done to someone somewhere doing
work.
Developing the codebase is a collaboration of everyone, not the
committers. The projects PMC/committers first job is to see to
submissions, make sure everything is legally clean, check builds.
There is a spectrum from making contributions/working on the code base
directly, through people testing development, people testing only
releases, to people who ask questions.
Why not use the minimal example as new test case ?
Rob has.
BTW: We are not able to implement a feature for the same application
because
of https://issues.apache.org/jira/browse/JENA-494
Contributions are always welcome, you are free to go look at the code and
provide a fix yourselves.
Yes. I am free to learn SPARQL Algebra, the inner workings and optimizations
of it in Jena, to get more familiar with Java and Java IDEs and then to fix
the things you guys overlooked. I'd prefer not to and to stay in Jena quality
management.
I'm glad you find the quality useful.
However, I could
1) pay my employee more familiar with Java to look into this and submit a fix
Yes - or contract someone else.
2) do a donation
3) put a bounty on it
What would you prefer ?
Everyone::
A practical step is to run your test suite against the development builds.
We'd very much appreciate receiving more tests we can include the test
suite. Obviously that's not possible with proprietary code or code that
relies on a specific infrastructure or databases.
The project builds automatically snapshots every night if anything has
changed.
It's moving from "good practice" to "standard practice" in open source
usage to run tests against the development snapshots as well as releases.
For a small amount of setup, there is return for the system relying on
Jena because that codebase is protected against bugs, random changes of
implicit assumptions etc. It helps the project by providing early feedback.
I hope you can setup up such testing. If there is anything that can
help make a easy process for you or any one else, then let's discuss it.
Andy
Regards,
Michael Brunnbauer
