Hi,
on a side note (it's Friday evening here, so maybe now I'll be doing something
"fun" [1]), it's great to report bugs and provide feedback in general.
I do sometimes report bugs to open source projects I use. If I am able, I submit
a patch, but I do not pretend or assume that just because I reported a bug, the
bug will be fixed. It's does not work like that. It depends on individuals and
here in Apache we are all individuals.
The "getting involved" [2] page on the Apache Jena website tries to show people
the path: submit bug reports/feedback >> use the SNAPSHOTs to stay on the
bleeding edge >> checkout the sources and get used to it >> look around at the
other open issues >> find something you care about or like and submit a patch
(repeat, repeat, ...) >> engage with other committers more >> learn more about
Apache and how it works >> ...
One of the principle in Apache is "meritocracy: literally, government by merit"
[3]. I think it's a good one, one I believe in.
Have a nice week-end,
Paolo
[1] http://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/branches/hash-ids/
[2] http://incubator.apache.org/jena/getting_involved/
[3] http://www.apache.org/foundation/how-it-works.html#meritocracy
Simon Helsen wrote:
I would like to see both
https://issues.apache.org/jira/browse/JENA-131
https://issues.apache.org/jira/browse/JENA-143
resolved
I provided input for 131 - I still have to try to produce a test-case for
143, but depending on the origin of 131, it may be connected to the
problem in 143
thanks
Simon
From:
Paolo Castagna <[email protected]>
To:
[email protected]
Date:
11/04/2011 09:21 AM
Subject:
What are the JIRA issues to fix before a release?
Hi,
today, I have time to work on Jena.
What are the JIRA issues to fix before a release?
Paolo
