harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konovalova, Svetlana" <svetlana.konoval...@intel.com>
Subject RE: [jira][general] Good issue resolution guideline update
Date Tue, 06 Feb 2007 11:29:06 GMT

+1 for adding this info to the "Good issue resolution  
guideline" [1]. 

But IMHO the "Reporting Issues" section is a better place. Right here we
mention that "A patch to test is highly appreciated." AFAIS, makes sense
to say here how to create patches. Don't you think that we should add,
let's say a "Patch creating tips" subsection to this section? 

BTW, we have one more page [2] providing "Guidelines on how to Create
and Submit a Patch". IMHO would be nice to merge these two pages to
collect related info in one place. I suggest to remove the "Guidelines
on how to Create and Submit a Patch" section [2] and add its content to
[1]; Also we could add a link from [2] to [1]. In this case, we would
have all detailed instructions on how to create and submit a patch in a
right way on one and the same page.
Any objections?  

[1] http://harmony.apache.org/issue_resolution_guideline.html
[2] http://harmony.apache.org/get-involved.html

On Feb 5, 2007, at 11:10 AM, Alexey Petrenko wrote:

> Guys,
> I think we need a little update for the "Good issue resolution  
> guideline" [1]
> I suggest the following additions to the "Resolving Issues.If the
> issue is a bug" to make committers life much easier :)
> 1. All the newly introduced message strings should be  
> internationalized
> 2. All the patches should have an evaluation comment
> 3. If you change two lines of code please make sure that you patch
> includes only these two lines and do not include any other changes
> like code formatting.
> 4. Add yourself to the list of watchers to receive comments and
> concerns on your patch.
> Thoughts? Concerns? Objections?
> SY, Alexey
> [1] http://harmony.apache.org/issue_resolution_guideline.html

View raw message