hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@yahoo-inc.com>
Subject Re: add incompatible flag to Jira
Date Fri, 21 Mar 2008 03:14:08 GMT

On Mar 18, 2008, at 12:18 PM, stack wrote:

>>> -----Original Message-----
>>> From: Nigel Daley [mailto:ndaley@yahoo-inc.com]
>>> Sent: Tuesday, March 11, 2008 11:49 AM
>>>
>>> Good idea Rob. I think these 2 ideas are orthogonal.  So I suggest
>>> these 2 additions to Jira:
>>>
>>> 1. an incompatible checkbox
>>> 2. a release note text box
>>>
>>> For an incompatible change, the submitter sets the field if the  
>>> patch
>>> is an incompatible change w/ the last major release.  The committer
>>> and submitter may need to discuss whether or not to set the
>>> incompatible flag once the actual "Fix Version" field is set.
>>> Guidance on what constitutes an incompatible change should be
>>> published on wiki.
>>>
>>>
>
> +1 Sounds good to me.
>
> (Would there be a means of ensuring all JIRAs with 'incompatible  
> change' checked get mention in CHANGES.txt INCOMPATIBLE CHANGES?)

That could be arranged.

>>> For release notes, the submitter should fill in release notable
>>> information (if any) for the patch.  An automated process can then
>>> put all the release notes into a file when a release is rolled.
>>> Guidance on what is release notable should be published on wiki.
>>>
>>>
>
> Also sounds good.  Would the release notes file be different from  
> CHANGES.txt?

Release notes would be the important/big/incompatible type changes.   
It would be supplied by the *submitter* as opposed to the  
*committer*.  It's also likely that it would be more verbose than our  
current CHANGES.txt.

> How would this file display when I click on 'Browse release notes  
> now!' on the releases.html page?

No idea.


Mime
View raw message