Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of mikhail.a.markov@gmail.com
 designates 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=aRzZLXaD5T60eX/NqDOQF4s2bcEbhe+JzDGVWDyV5HQANDMEIsIIp7VqMkIUJrqNkkW4rxHe2mr0fimamFXO565TxkvR0d1FiXmakN6utUJiA5uK9BkJdOCU+nZr7br9st3VdgDQzDmZEkcCSwveE1QuktGZz1P4jIAoBwzLUMI=
Message-ID: <51abf0750612140600y8d36cb0p9a0faa43cd7e4093@mail.gmail.com>
Date: Thu, 14 Dec 2006 17:00:59 +0300
From: "Mikhail Markov" <mikhail.a.markov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [general] Wise JIRA processing
In-Reply-To: <469bff730612140554u6b065fe1ldd5fad4962096387@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_158711_19855985.1166104859598"
References: <51abf0750612132224x6f087cbbwab1f99f9d664aaf2@mail.gmail.com>
	 <c3755b3a0612140136i551e0693g5b58af51b9de805f@mail.gmail.com>
	 <51abf0750612140458q413ca6can725f40038eac89c5@mail.gmail.com>
	 <c3755b3a0612140532y6de6341fy7a6cc330812aef55@mail.gmail.com>
	 <51abf0750612140544s23be9907kac7d4457b19c853e@mail.gmail.com>
	 <469bff730612140554u6b065fe1ldd5fad4962096387@mail.gmail.com>

------=_Part_158711_19855985.1166104859598
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This is even better!
+1

Regards,
Mikhail


On 12/14/06, Pavel Ozhdikhin <pavel.ozhdikhin@gmail.com> wrote:
>
> I support Milhail's proposal - the possibility to work directly with JIRA
> issuess looks attractive to me. Probably we should not allow to close JIRA
> issues to everyone - it can be done by the committer who integrated the
> patch. Let's let everyone to assign the issue to him/herself, set patch
> available status - everything that is needed for every day work with an
> issue.
>
> Thank you,
> Pavel
>
> On 12/14/06, Mikhail Markov <mikhail.a.markov@gmail.com> wrote:
> >
> > On 12/14/06, Alexey Petrenko <alexey.a.petrenko@gmail.com> wrote:
> > >
> > > 2006/12/14, Mikhail Markov <mikhail.a.markov@gmail.com>:
> > > > On 12/14/06, Alexey Petrenko <alexey.a.petrenko@gmail.com> wrote:
> > > > >
> > > > > 1. How will we choose people to give "contributor" access to JIRA?
> > > > This should be discussed here :-). One of the easiest possible
> > solutions
> > > is
> > > > to automatically grant this access after particular number of posts
> to
> > > dev
> > > > list + actions with JIRAs.
> > > As we all knows number of posts does not tell anything about the
> person
> > :)
> >
> >
> > Agree, but this could be an indicator for considering the person as a
> > candidate for JIRA contributor
> >
> >
> > > Another option is to use the same procedure as for granting committer
> > > > status (but have less strict requirements).
> > > OK
> > >
> > > > 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?
> > > > The main point is to quicker process JIRAs not requiring committing
> to
> > > svn +
> > > > some small things like
> > > > "Patch available"
> > > I see two solutions here:
> > > 1. Ask bug creator to set this flag if he/she happy with the
> resolution.
> > > 2. Let set this tag to everybody (if it is possible)
> > >
> > > I like first one more.
> >
> >
> > I prefer the second one :-) We could make a separate thread on this.
> >
> >
> > > "In progress" tags.
> > > I think we can let to set this flag to everybody.
> > > And this is probably a good idea!
> >
> >
> > Agree (we could discuss this in the same separate thread as the above
> > question.
> >
> > Thanks,
> > Mikhail
> >
> >
> > SY, Alexey
> > >
> >
> >
>
>

------=_Part_158711_19855985.1166104859598--