I agree, Assignee has been used primarily to give recognition to the
contributor who ended up submitting the patch which got merged.
Typically jira's remain unassigned - even if it were to be assigned, it
conveys no meaning or ownership or ongoing work : IMO it is equivalent to
an unassigned
I don't believe Assignee has ever been used for anything except to give a
bit of informal credit to the person who drove most of the work on the
issue, when it's resolved.
If that's the question - does Assignee mean only that person can work on
the issue? then no, it has never meant that.
You say
(Actually the real world case was fixed somehow and I wouldn't like to
point out a fixed one. I just would like to make sure what I think is
correct and is considered as "consensus".)
Just consider the case as simple - someone files two different JIRA issues
for new features and assigns to
I think it's OK to raise particular instances. It's hard for me to evaluate
further in the abstract.
I don't think we use Assignee much at all, except to kinda give credit when
something is done. No piece of code or work can be solely owned by one
person; this is just ASF policy.
I think we've
Thanks for the input, Hyukjin!
I have been keeping my own policy among all discussions I have raised - I
would provide the hypothetical example closer to the actual one and avoid
pointing out directly. The main purpose of the discussion is to ensure our
policy / consensus makes sense, no more. I
I remember I raised a similar issue a long time ago in the dev mailing
list. I agree that setting no assignee makes sense in most of the cases,
and also think we share similar thoughts about the assignee on
umbrella JIRAs, followup tasks, the case when it's clear with a design doc,
etc.
It makes
Hi devs,
I'd like to raise a discussion and hear voices on the "assignee" practice
on committers which may lead issues on preemption.
I feel this is the one of major unfairnesses between contributors and
committers if used improperly, especially when someone assigns themselves
with multiple JIRA
