Division
-Original Message-
From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 10:56 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Alexey,
I agree
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 10:37 AM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Alexey,
Thanks for the patch
for the patch
Best regards,
Sveta
-Original Message-
From: Ivanov, Alexey A [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 11:18 AM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 7:01 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
I've just submitted a new
@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 7:01 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 2:33 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Alexey,
Thank you so much
(was:
[classlib]volunteer to supply patches for old JIRAs)
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 7:01 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply
Software Division
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 3:50 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Alexey
, Alexey A [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 5:20 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Sveta, all,
I've attached the updated patch to the JIRA.
Please review
, November 09, 2006 5:20 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Sveta, all,
I've attached the updated patch to the JIRA.
Please review.
Regards,
Alexey.
P.S. By the way, do we really
, November 07, 2006 1:32 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
I've published Good issue resolution guideline on Harmony site:
http://incubator.apache.org/harmony
08, 2006 1:50 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Hi,
Do we really need a smiley in the header: Resolution Provider :)?
AFAIK, for headings one should use Title Capitalization, i.e
,
Sveta
-Original Message-
From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 11:18 AM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Good! Go ahead. Do you
I've published Good issue resolution guideline on Harmony site:
http://incubator.apache.org/harmony/issue_resolution_guideline.html
(wait for a while for the web site synchronization). It is not linked
to other pages yet.
So comments to guideline and link place suggestions are welcome.
SY,
:32 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
I've published Good issue resolution guideline on Harmony site:
http://incubator.apache.org/harmony/issue_resolution_guideline.html
(wait
] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
I've published Good issue resolution guideline on Harmony site:
http://incubator.apache.org/harmony/issue_resolution_guideline.html
(wait for a while for the web site synchronization). It is not linked
@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Nadya,
we definetly need a link to this page. That's not a question.
Question is where to place the link.
And as I said in previous email link place suggestions
@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Nadya,
we definetly need a link to this page. That's not a question.
Question is where to place the link.
And as I said in previous email link place suggestions
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
:)
Yes, I'll prepare a patch.
2006/9/28, Geir Magnusson Jr. [EMAIL PROTECTED]:
On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
Guys,
Since there is no additional comments
-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 2:03 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
2006/11/6, Fedotov, Alexei A [EMAIL PROTECTED
, November 06, 2006 2:03 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
2006/11/6, Fedotov, Alexei A [EMAIL PROTECTED]:
Alexey,
I started looking into this thread. Are guidelines on the web site
, 2006 2:03 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
2006/11/6, Fedotov, Alexei A [EMAIL PROTECTED]:
Alexey,
I started looking into this thread. Are guidelines on the web site
PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
:)
Yes, I'll prepare a patch.
2006/9/28, Geir Magnusson Jr. [EMAIL PROTECTED]:
On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
Guys
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony site and wiki.
I prefer wiki because it will be easy to edit it and I can put it
there myself :)
Thoughts?
SY, Alexey
2006/9/26, Alexey Petrenko [EMAIL PROTECTED]:
I've
, September 28, 2006 11:21 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony site
PROTECTED]
Sent: Thursday, September 28, 2006 11:21 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Guys,
Since there is no additional comments on this guideline...
Let's put
(was:
[classlib]volunteer to supply patches for old JIRAs)
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony site and wiki.
I prefer wiki because it will be easy to edit it and I can put it
there myself :)
Thoughts
:21 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony
On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony site and wiki.
I prefer wiki because it will be easy to edit it and I can put it
there myself :)
And if you put in a
:)
Yes, I'll prepare a patch.
2006/9/28, Geir Magnusson Jr. [EMAIL PROTECTED]:
On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
Guys,
Since there is no additional comments on this guideline...
Let's put it somewhere.
We got two options: Harmony site and wiki.
I prefer wiki because
This version looks good to me.
Regards,
2006/9/26, Alexey Petrenko [EMAIL PROTECTED]:
I've combined all the comments again.
And here is the last version. I hope... :)
=== cut ===
Preface
This guideline covers a wide range of issues but not all of them.
If you cannot do one of the steps, then
I've combined all the comments again.
And here is the last version. I hope... :)
=== cut ===
Preface
This guideline covers a wide range of issues but not all of them.
If you cannot do one of the steps, then write a comment to the issue.
Use your common sense!
Issue reporter:
1. Explicitly
On Sep 21, 2006, at 1:30 AM, Alexey Petrenko wrote:
2006/9/20, Geir Magnusson Jr. [EMAIL PROTECTED]:
I still don't think that people should only be notifying the
community about indications of interest or such only in the JIRA.
Sending mail to the dev list should also be in there.
Do we
Alexei Zakharov wrote:
Hi Alexey,
IMHO it would be nice to explicitly state (for issue reports and/or
resolution providers) that patch to classlib code and patch to test
should be two separate patches. I personally posted several combined
patches in the past. :)
My preference is for
Alexey Petrenko wrote:
2006/9/20, Geir Magnusson Jr. [EMAIL PROTECTED]:
I still don't think that people should only be notifying the
community about indications of interest or such only in the JIRA.
Sending mail to the dev list should also be in there.
Do we really need that? I'm afraid that
2006/9/21, Tim Ellison [EMAIL PROTECTED]:
Alexei Zakharov wrote:
Hi Alexey,
IMHO it would be nice to explicitly state (for issue reports and/or
resolution providers) that patch to classlib code and patch to test
should be two separate patches. I personally posted several combined
patches
YES PLEASE :)
On Sep 21, 2006, at 6:37 AM, Alexei Zakharov wrote:
Hi Alexey,
IMHO it would be nice to explicitly state (for issue reports and/or
resolution providers) that patch to classlib code and patch to test
should be two separate patches. I personally posted several combined
patches in
On Sep 21, 2006, at 9:42 AM, Tim Ellison wrote:
Alexei Zakharov wrote:
Hi Alexey,
IMHO it would be nice to explicitly state (for issue reports and/or
resolution providers) that patch to classlib code and patch to test
should be two separate patches. I personally posted several
combined
How does it help to attach them separately?
Just to implement the algorithm for committers described earlier by Alexey:
2. Issue is a bug:
2.1. If a patch to test is available, apply it.
2.2. Check that the test fails.
2.3. Apply the fix for the issue.
2.4. Check that test succeeds now.
Alexei Zakharov wrote:
How does it help to attach them separately?
Just to implement the algorithm for committers described earlier by Alexey:
2. Issue is a bug:
2.1. If a patch to test is available, apply it.
2.2. Check that the test fails.
2.3. Apply the fix for the issue.
2.4.
On Sep 21, 2006, at 3:27 PM, Tim Ellison wrote:
Alexei Zakharov wrote:
How does it help to attach them separately?
Just to implement the algorithm for committers described earlier
by Alexey:
2. Issue is a bug:
2.1. If a patch to test is available, apply it.
2.2. Check that the test
Geir Magnusson Jr. wrote:
I do. what tool do you suggest?
I use Eclipse and TortoiseSVN patch tools at different times. Both
allow you to read a combined patch, but update only a subset of affected
files.
Like I said though, I don't feel strongly so recommending separate
patches is ok by me
I've combined all the ideas. And here is the result.
=== cut ===
Preface
This guideline covers a wide range of issues but not all of them.
If you cannot do one of the steps, then write a comment to the issue.
Use your common sense!
Issue reporter:
1. Explicitly state the expected behavior and
2.4. All the pacthes (test and fix) should be relative to the
directory where the main build.xml is:
https://svn.apache.org/repos/asf/incubator/harmony/enhanced/classlib/trunk
As Mark noted, the directory where the module's build.xml is located
is also acceptable.
Not module build.xml but the main build.xml.
Anyway since we got a lot of directories except of modules it is
better to make a diff from the root.
2006/9/20, Oleg Khaschansky [EMAIL PROTECTED]:
2.4. All the pacthes (test and fix) should be relative to the
directory where the main build.xml is:
On 20 September 2006 at 13:56, Alexey Petrenko [EMAIL PROTECTED] wrote:
Not module build.xml but the main build.xml.
Anyway since we got a lot of directories except of modules it is
better to make a diff from the root.
I anticipate that in time we will have people that only check out the
Then we should remove this requirement at all...
Since it is possible to have a patches for a few modules at once. Or
for a few modules and a doc.
2006/9/20, Mark Hindess [EMAIL PROTECTED]:
On 20 September 2006 at 13:56, Alexey Petrenko [EMAIL PROTECTED] wrote:
Not module build.xml but the
Alexey,
What was wrong with the initial suggestion of recommending patches
be either relative to the classlib/trunk or
classlib/trunk/module/module-name?
I really don't care much *except* that there were two specific types
of patches I was trying to avoid as I mentioned when I first suggested
I still don't think that people should only be notifying the
community about indications of interest or such only in the JIRA.
Sending mail to the dev list should also be in there.
Also, we should as people to name patch files as HARMONY-
JIRA#_whatever_.patch It's very helpful.
On Sep
On 15 September 2006 at 8:08, Alexey Petrenko
[EMAIL PROTECTED] wrote:
2006/9/15, Gregory Shimansky [EMAIL PROTECTED]:
On Thursday 14 September 2006 16:55 Mark Hindess wrote:
I'd suggest two further things.
First, we change the default JIRA priority to something lower
than 'Major'.
On 15 September 2006 at 12:18, Vladimir Gorr [EMAIL PROTECTED] wrote:
I'd like to add some words ...
IMO each contributor should be responsible his patch can be applied
w/o any problems. That's why he should check these patches and run
the tests before filling new JIRA issue. However
On 9/15/06, Mark Hindess [EMAIL PROTECTED] wrote:
On 15 September 2006 at 12:18, Vladimir Gorr [EMAIL PROTECTED] wrote:
I'd like to add some words ...
IMO each contributor should be responsible his patch can be applied
w/o any problems. That's why he should check these patches and run
Yes, I don't think it would hurt, even if it's in the patch as Mark noted.
geir
Vladimir Gorr wrote:
On 9/15/06, Mark Hindess [EMAIL PROTECTED] wrote:
On 15 September 2006 at 12:18, Vladimir Gorr [EMAIL PROTECTED] wrote:
I'd like to add some words ...
IMO each contributor should be
Thanks Alexey - I think these guidelines will be helpful for all of
us, whether opening, fixing or committing bugs and patches.
Just a couple of extra comments.
Alexey Petrenko wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony
2006/9/13, Alexey Petrenko [EMAIL PROTECTED]:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help committers to spend less time on
applying other's patches.
As a
On 9/13/06, Nathan Beyer [EMAIL PROTECTED] wrote:
-Original Message-
From: Jimmy, Jing Lv [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 12:07 AM
IIRC, there's a open JIRA of management, it is because Harmony
java.lang.management does not exist yet, please ignore.
I'd suggest two further things.
First, we change the default JIRA priority to something lower than
'Major'. Currently most come in as 'Major' even if they are trivial
edge cases that might never affect an application. I assume because
people are just leaving the default unchanged without
Agree on both cases.
We can also ask to use dos2unix utility on Windows to convert patches
to unix LF fromat.
SY, Alexey
2006/9/14, Mark Hindess [EMAIL PROTECTED]:
I'd suggest two further things.
First, we change the default JIRA priority to something lower than
'Major'. Currently most come
On 14 September 2006 at 17:13, Alexey Petrenko [EMAIL PROTECTED] wrote:
Agree on both cases.
We can also ask to use dos2unix utility on Windows to convert patches
to unix LF fromat.
I'm actually less worried about this one. I tend to be able to get any
patch to work under linux using either
On Thursday 14 September 2006 16:55 Mark Hindess wrote:
I'd suggest two further things.
First, we change the default JIRA priority to something lower than
'Major'. Currently most come in as 'Major' even if they are trivial
edge cases that might never affect an application. I assume because
2006/9/15, Gregory Shimansky [EMAIL PROTECTED]:
On Thursday 14 September 2006 16:55 Mark Hindess wrote:
I'd suggest two further things.
First, we change the default JIRA priority to something lower than
'Major'. Currently most come in as 'Major' even if they are trivial
edge cases that
I'd like to add some words ...
IMO each contributor should be responsible his patch can be applied w/o any
problems.
That's why he should check these patches and run the tests before
filling new JIRA issue.
However nobody can guarantee either patch will be successfully applied later
due to the
Paulex Yang 写道:
Nathan Beyer 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
I think that we should close non-bug defferencies as wont fix or
something like that.
2006/9/13, Spark Shen [EMAIL PROTECTED]:
Paulex Yang 写道:
Nathan Beyer 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.
to split JIRA 921 into two JIRAs. One for DRLVM, one for
IBM vm.
Any suggestions?
-Nathan
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 10:26 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib]volunteer to supply patches
Spark Shen wrote:
Paulex Yang 写道:
Nathan Beyer 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
Spark Shen wrote:
Paulex Yang 写道:
Nathan Beyer 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
Geir Magnusson Jr. 写道:
Spark Shen wrote:
Paulex Yang 写道:
Nathan Beyer 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
: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many unresolved JIRAs
suggestions?
-Nathan
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL
-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many
the patch.
-Nathan
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote:
Tony Wu 写道
[mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many
a
comment supporting the patch.
-Nathan
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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
@incubator.apache.org
Subject: Re: [classlib]volunteer to supply patches for old JIRAs
On 9/13/06, Spark Shen [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many unresolved JIRAs posted so long time.
I
purpose to
dive into and find whether
.
-Nathan
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED
: 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 [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many unresolved JIRAs
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help committers to spend less time on
applying other's patches.
As a start we can take Nathan's post with additions from
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help committers to spend less time on
applying other's patches.
And the resolution provider should not forget to add a comment when he
is starting development of the patch to prevent collisions. If the
resolution provider is a committer he simply assigns the bug.
On 9/13/06, Andrew Zhang [EMAIL PROTECTED] wrote:
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED]
and resolution provider should verify the application.
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help committers to spend less time on
applying other's patches.
As
and resolution provider should verify the application.
Or, probably, the reporter may do it also.
On 9/13/06, Tony Wu [EMAIL PROTECTED] wrote:
and resolution provider should verify the application.
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create
2006/9/13, Richard Liang [EMAIL PROTECTED]:
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will help committers to
On Wednesday 13 September 2006 18:09 Andrew Zhang wrote:
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare good fixes and will
Make your addition to the guideline.
SY, Alexey
14.09.06, Gregory Shimansky[EMAIL PROTECTED] написал(а):
On Wednesday 13 September 2006 18:09 Andrew Zhang wrote:
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue
Gregory Shimansky wrote:
On Wednesday 13 September 2006 18:09 Andrew Zhang wrote:
On 9/13/06, Alexey Petrenko [EMAIL PROTECTED] wrote:
Guys,
I think that we need to create something like Good issue resolution
guideline and post it on Harmony site or wiki. It will help community
to prepare
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?
--
Tony Wu
China Software Development Lab, IBM
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
On 9/13/06, Tony Wu [EMAIL PROTECTED] wrote:
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 :)
Great!
Is there anyone alse has interest and would like to work with
Andrew Zhang 写道:
On 9/13/06, Tony Wu [EMAIL PROTECTED] wrote:
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 :)
Great!
Is there anyone alse has interest and would
On 9/13/06, Spark Shen [EMAIL PROTECTED] 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
Andrew Zhang 写道:
On 9/13/06, Spark Shen [EMAIL PROTECTED] 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
Hi, all:
I am also ready to fix unresolved JIRAs.
Currently, my work focuses on java.lang module.
On 9/13/06, Spark Shen [EMAIL PROTECTED] wrote:
Andrew Zhang 写道:
On 9/13/06, Spark Shen [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed there're many unresolved JIRAs posted
Leo Li 写道:
Hi, all:
I am also ready to fix unresolved JIRAs.
Currently, my work focuses on java.lang module.
Hi Leo,
I also work on java.lang module. May be you could list which JIRAs you
are interested in, then we will not
deal with the same JIRA at the same time.
Best regards
On 9/13/06,
On 9/13/06, Spark Shen [EMAIL PROTECTED] 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
-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] wrote:
Tony Wu 写道:
Hi all,
I noticed
Nathan Beyer 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
Subject: Re: [classlib]volunteer to supply patches for old JIRAs
On 9/13/06, Spark Shen [EMAIL PROTECTED] 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
1 - 100 of 109 matches
Mail list logo
