Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.82.229 as permitted sender)
DomainKey-Status: good
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=gGq7pVQbr0MRy8EvEn7x8nO4SUp4AABev8vyuqjjfGMRImgXSB4/vsrWYHZ2yLLdwHwnHWQHVXiM8/9u+Akcom5IyDZj6R0fDq1Yb+WBliA2Qua7Wh1vQzcR6VuVQFXelXYE9c1pO9GIX06bgUZndJt4CesQZXYkYrugy3q+Bs8=
Message-ID: <211709bc0609130642k529456cbge2894ef72de375e1@mail.gmail.com>
Date: Wed, 13 Sep 2006 21:42:17 +0800
From: "Tony Wu" <wuyuehao@gmail.com>
To: harmony-dev@incubator.apache.org, geir@pobox.com
Subject: Re: [classlib]volunteer to supply patches for old JIRAs
In-Reply-To: <45080599.1040500@pobox.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_228878_26146314.1158154937083"
References: <211709bc0609122026i238af5a7q9ac6357b7b995cec@mail.gmail.com>
	 <006c01c6d6e9$7b5c7a20$0401a8c0@LITTLEGUY>
	 <211709bc0609122129r1e49c8a7qad6f27095e7b0337@mail.gmail.com>
	 <45079979.8090506@pobox.com>
	 <211709bc0609130615h7b97bb0dv9e6a59f0dafd688@mail.gmail.com>
	 <45080599.1040500@pobox.com>

------=_Part_228878_26146314.1158154937083
Content-Type: text/plain; charset=ISO-2022-JP; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

oops!
may be just record *someone is in the JIRA* is more lightweight. I'll fix
it.
any suggest is welcome: )

On 9/13/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
>
> My suggestion is to use the wiki page to augment rather than replace
> what the JIRA can do.
>
> For example, I'd suggest that people who are working on a given JIRA
> note that *in the JIRA*.
>
> geir
>
>
> Tony Wu wrote:
> > I have opened a new page at harmony wiki,
> > http://wiki.apache.org/harmony/OLDJIRAS
> > You can get the guideline, the process and a list of old jira issues
> there.
> > In the list there is a column called ASSIGNEE, you can sign your name
> there
> > if you are working on that issue. And you may check from this list to
> > ensure
> > there is no one also decide to working on the same issue before you
> start.
> >
> > If you notice there is something wrong or I missed, feel free to update
> > that
> > page, your effort will bring convenience to whole harmony community: )
> >
> >
> > On 9/13/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
> >>
> >> You might also consider creating a page on the wiki where you outline
> >> this process, and record who is signing up for what...
> >>
> >> geir
> >>
> >>
> >> Tony Wu wrote:
> >> > so helpful suggestion, thank you Nathan.
> >> > According to Nathan's suggestion, I suggest we go ahead as below,
> >> > 1. verify all the issues without patch, supply a patch if possible.
> >> > 2. for the issues already has a patch, verify the reason why it was
> >> > ignored,
> >> > and then
> >> > a.write testcase if caused by lack of test.
> >> > b.supply another patch if the patch is out of date.
> >> > c.add comments to support it if the patch is ok.
> >> >
> >> >
> >> > On 9/13/06, Nathan Beyer <nbeyer@kc.rr.com> wrote:
> >> >>
> >> >> Here are a few things that I think might help with getting through
> >> >> some of
> >> >> the older outstanding issues, as well as new ones.
> >> >>
> >> >> * If an issue is old (over a month???), then verify that it's still
> an
> >> >> issue
> >> >> with the latest code and note this with a JIRA comment.
> >> >> * Obviously posting patches is great, but patches without tests are
> >> >> almost
> >> >> always ignored.
> >> >> ** If you're posting an enhancement, post a patch that enhances the
> >> tests
> >> >> and make sure they pass on an RI. (I always make sure the test
> passes
> >> on
> >> >> the
> >> >> RI before considering the patch.)
> >> >> ** If you're posting a fix, post a patch that includes a regression
> >> test.
> >> >> (I
> >> >> always apply the test first, then run it to see it fail, then I
> >> look at
> >> >> the
> >> >> fix.)
> >> >> * If there's a particular JIRA issue that you would like fixed and a
> >> >> patch
> >> >> already exists, try applying the patch yourself, verify it and then
> >> add
> >> a
> >> >> comment supporting the patch.
> >> >>
> >> >>
> >> >> -Nathan
> >> >>
> >> >> > -----Original Message-----
> >> >> > From: Tony Wu [mailto:wuyuehao@gmail.com]
> >> >> > Sent: Tuesday, September 12, 2006 10:26 PM
> >> >> > To: harmony-dev@incubator.apache.org
> >> >> > Subject: Re: [classlib]volunteer to supply patches for old JIRAs
> >> >> >
> >> >> > On 9/13/06, Spark Shen <smallsmallorgan@gmail.com> wrote:
> >> >> > >
> >> >> > > Tony Wu 写道:
> >> >> > > > Hi all,
> >> >> > > > I noticed there're many unresolved JIRAs posted so long time.
> I
> >> >> > > > purpose to
> >> >> > > > dive into and find whether it is in my range and try to supply
> a
> >> >> patch
> >> >> > > > if no
> >> >> > > > one objects :)
> >> >> > > > Is there anyone alse has interest and would like to work with
> >> me?
> >> >> > > >
> >> >> > > Hi,
> >> >> > > It is interesting of your proposal. May I join in?
> >> >> >
> >> >> >
> >> >> > Great! Welcome!
> >> >> >
> >> >> > I noticed that there are many categories of components. I suggest
> we
> >> >> > > only deal with those components we are familier with.
> >> >> > > Since there are so many unresolved JIRAs, will you start from
> the
> >> >> > > beginning and I will start from the end. If someone else is
> >> >> interested,
> >> >> > > he/she may start from the middle. :-)
> >> >> >
> >> >> >
> >> >> > good idea, I'll start to look in descendent order of jira sn.
> >> >> >
> >> >> >
> >> >> > Best regards
> >> >> > >
> >> >> > > --
> >> >> > > Spark Shen
> >> >> > > China Software Development Lab, IBM
> >> >> > >
> >> >> > >
> >> >> > >
> >> ---------------------------------------------------------------------
> >> >> > > Terms of use : http://incubator.apache.org/harmony/mailing.html
> >> >> > > To unsubscribe, e-mail:
> >> harmony-dev-unsubscribe@incubator.apache.org
> >> >> > > For additional commands, e-mail:
> >> >> harmony-dev-help@incubator.apache.org
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Tony Wu
> >> >> > China Software Development Lab, IBM
> >> >>
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> >> >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> >> >> For additional commands, e-mail:
> harmony-dev-help@incubator.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>


-- 
Tony Wu
China Software Development Lab, IBM

------=_Part_228878_26146314.1158154937083--