Hi
Andy Seaborne wrote:
On 10/11/11 19:29, Paolo Castagna wrote:
Hi Andy
Andy Seaborne wrote:
Paolo,
Setting the version to something unrelated to the component is
confusing and mis-communicates.
1/ It's not the components version number
Good point, let's try with "component + version number".
An issue can be said to "fix" 0, 1 or more "component + versions":
https://issues.apache.org/jira/browse/JENA#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
2/ Is it your opinion or are you making a personal commitment?
See "Assignee" field for that.
Surely the "vote" button is for what someone would like to see happen.
I use the "vote" button to say: "oh, yeah, I'd love to see this fixed as
soon as possible (but I cannot do it right now, or I do not know how to
do it, or for any other reasons I am not going to do it, but, please,
please, someone... fix this! ;-)).
Sometimes I also use the "vote" button to acknowledge a problem and say:
"oh, yeah, I experience this problem myself".
Assigning something to myself is even stronger than a "vote" for an issue:
"oh, yeah... I'd love to see this fixed and I take action. I assign the
issue to myself and I am going to fix this, hopefully, as soon as possible".
This tells others I am prepared to work on this and I care about that issue.
Also, if an issue is assigned to me but for any reason I am slow and I am
slowing you or the project down in fixing that issue... "work stealing" from
me is welcome by me. :-) No offense, really! Having said that, I realize
this might not be true for others so I tend not to do it. I did it once here
just to experiment and see if there was any reaction. I assume silent as
consensus. But, in general, is a practice I do not think we need to encourage.
Work stealing can be a waste of time and upset people in particular if someone
has already started working on something and it's almost done.
Some issues (not many), for one reasons or another, remain open for a longer
period of time, but I do not see that as a problem in particular if they do
not block releases or other issues and if they are more exploratory,
new features or investigation in nature:
- https://issues.apache.org/jira/browse/JENA-117
- https://issues.apache.org/jira/browse/JENA-10
- ...
I have mixed feelings about these, but I think a small number of forward
looking JIRA issues do not cause too much noise or problems and I find it
useful to have them in JIRA. Once again, if we agree this is not good I'll
go ahead and remove those. I hope this will not be necessary, so long the
list of such issues remain short.
What do you think?
I am sorry for these emails and questions, but I do believe it's important to
make some of these thoughts and practices explicit and see if we (as a project)
agree on these and find them useful. Once we are all on the same page on these
things, there is no need for this sort of emails... but so far I did not see
many discussions of these topics and IMHO are very, very, important from a
community point of view. They don't get JIRA issues fixed and might slow down
a little bit progress on the software... but it's not only about the software,
indeed the software is important, but it's the people around the software that
are more important and how well and effectively they work together (remotely).
Paolo
Andy
