geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy" <c1vams...@gmail.com>
Subject Re: A general question?
Date Tue, 28 Feb 2006 04:48:27 GMT
I would suggest that once the patch is committed, one of the commiter, the
contributor and the reporter, whoever verifies that the patch does solve the
issue, can mark the issue as "resolved".  This will definitely cut the
waiting time short.

-Vamsi

On 2/28/06, Jacek Laskowski <eljotpl@gmail.com> wrote:
>
> 2006/2/27, anita kulshreshtha <a_kulshre@yahoo.com>:
>
> >     In this case the committer would mark the Jira
> > issue as resolved/invalid/fixed or whatever the case
> > may be.
>
>
> > IIUC, you are saying that the contributors can
> > mark the issue as 'resolved' to indicate that the
> > issue has been resolved to their satisfaction and wait
> > for the committers to look at their patch.
>
> Correct.
>
> Technically, a contributor may (can) resolve an issue w/ patch, and
> wait till a committer closes it, which in my opinion means the patch
> is committed with or without some changes. It's how permissions work
> in JIRA and it's nothing to do with the access to the repo. But, since
> you can't submit your changes to the repo, there's no way for
> non-committer to close issues (which I understand as submition of
> patches).
>
> There's another way to work with issues/patches. A contributor submits
> a patch, then a committer commits it to the repo, and they both await
> the reporter's response if it satisfies him/her.
>
> I'd prefer the second approach.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.laskowski.org.pl
>

Mime
View raw message