Alexey Petrenko wrote:
2006/12/14, Tony Wu <[EMAIL PROTECTED]>:
There is another problem. I'm able to mark an issue as Patch Available
only if the issue is reported by myself. So it is hard for committers
to find out these issuses which have a patch already but without the
mark, that is, the Patch Availalbe has not been fully used, I think.
Yes, this is a problem...
How about sending mail to the list saying there's a patch? :)
geir
SY, Alexey
On 12/14/06, Alexey Petrenko <[EMAIL PROTECTED]> wrote:
> 1. How will we choose people to give "contributor" access to JIRA?
> 2. As far as I understood the main point here is to give a possibility
> for non-committers to assign bugs. So non-committers can search for
> non-assigned bugs. Right?
>
> SY, Alexey
>
> 2006/12/14, Mikhail Markov <[EMAIL PROTECTED]>:
> > HI!
> >
> >
> > In my opinion, it's hard to track open JIRAs now.
> >
> >
> > For example, if the JIRA is not assigned then there is no simple
way to
> > understand if there's activity in there except opening it in
web-browser and
> > reading comments.
> > Only committers could modify the status of JIRAs and put them "In
progress"
> > mode. As we have not so many committers they could not monitor
large number
> > of open JIRA.
> >
> >
> > One of possible solutions is implemented in Apache Geronimo
project: there
> > is so called "JIRA contributor" role when the person could modify
JIRAs like
> > committers (close/reopen JIRA, modify it's status etc.) but could
not commit
> > the code to the repository.
> >
> > This role seems intermediate between contributor and committer
ones, some
> > kind of "committer kindergarten" :-).
> >
> > I think that for better processing JIRA issues we could implement
similar
> > role in Harmony (or invent something better).
> >
> >
> >
> > What do you think?
> >
> >
> >
> > Regards,
> >
> > Mikhail
> >
> >
>
--
Tony Wu
China Software Development Lab, IBM
