hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@altiscale.com>
Subject Re: auto-generating changes.txt was: migrating private branches to the new git repo
Date Fri, 05 Sep 2014 18:53:04 GMT

On Sep 5, 2014, at 9:19 AM, Karthik Kambatla <kasha@cloudera.com> wrote:

> On Thu, Sep 4, 2014 at 8:37 AM, Allen Wittenauer <aw@altiscale.com> wrote:
>>        We do need to have a talk about 3.x though.  Looking over the
>> list, it would appear that a lot of (what became) early 2.x JIRAs were
>> marked as Fixed against 3.x.  Probably 2/3’rd of the JIRAs showing up!  I
>> think it may be safe to just say “everything before date X should be set to
>> 2.x”, but I’m not sure of what that date would be.  Doing that would chop
>> the 3.x change list down to a much more realistic size, esp when compared
>> to the manual changes file.
> Would it help to look at the git commits for a release, and fetch the
> corresponding details from JIRA for those commits that have a JIRA #?

	Another thought I had was to see how many of these actually show up in the current changes
file and set them appropriately.  

	Then there is stuff like YARN-154….

	In either case, it’s likely going to be a manual process going through these. :(

	*rolls up sleeves*
View raw message