hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Junping Du <...@hortonworks.com>
Subject Re: [VOTE] Release Apache Hadoop 2.7.2 RC2
Date Sun, 17 Jan 2016 00:57:32 GMT
In addition, all new fixes backport from 2.6.3 doesn't listed in 2.7.2 entry of CHANGES.txt
but keep listed as 2.6.3. I think this is fine no matter we have multiple entries to track
the same commit or a single entry to track the earliest commit. The only thing matter is the
commits in release notes (coming from JIRA's Fix Versions) are matching with commits that
actually land on the branch and each commit is tracked in some entry on CHANGES.txt. I did
manually check that all 155 fixes are existing in commit log and we have entry in CHANGES.txt
to track each commit on 2.7.2. 
Let's keep focusing on deployment test of 2.7.2. Thanks!

Thanks,

Junping
________________________________________
From: Akira AJISAKA <ajisakaa@oss.nttdata.co.jp>
Sent: Saturday, January 16, 2016 7:39 PM
To: common-dev@hadoop.apache.org
Cc: hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Hi Xiao,

 >  From a quick comparison between the releasenotes.html and the
CHANGES.txt
 > files in source tarball, the number of total JIRAs is quite different.

In CHANGES.txt, JIRAs fixed in 2.6.1/2.6.2 are not in 2.7.2.
That is why the number of JIRAs are different.

Regards,
Akira

On 1/16/16 09:11, Xiao Chen wrote:
> Thanks Vinod for preparing the release package.
>
>
> +1 (non-binding).
>
> I verified the following:
>
>
>     - Successfully downloaded source tarball, verified md5
>     - Ran `mvn apache-rat:check` on source tarball, passed
>     - Successfully built from source tarball
>     - Successfully started a pseudo distributed cluster
>     - Ran some basic hdfs operations, then successfully ran a distcp
>
>
> 1 question:
>  From a quick comparison between the releasenotes.html and the CHANGES.txt
> files in source tarball, the number of total JIRAs is quite different.
> Seems like CHANGES.txt misses some of the fixes, because Searching
> <https://issues.apache.org/jira/browse/YARN-4434?jql=project%20in%20(HDFS%2C%20HADOOP%2C%20MAPREDUCE%2C%20YARN)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%202.7.2>
> 'project
> in (HDFS, HADOOP, MAPREDUCE, YARN) AND resolution = Fixed AND fixVersion =
> 2.7.2' from JIRA agrees with releasenotes.html (count=155).
>
> Here is how I did the check:
>
>
>     -  cat ~/Downloads/releasenotes.html |grep "
>     https://issues.apache.org/jira/" | awk -F ">" '{print $3}'|awk -F "<"
>     '{print $1}' |wc -l
>
>               returns 155
>
>
>     - for f in `find . -name CHANGES.txt |grep -v target`; do cat $f |grep
>     -B 10000 "Release 2.7.1" |grep .*-[0-9] |grep -v "Release 2.7" ; done|wc -l
>
>              returns 103
>
> I'm not sure whether this is a problem or not.
> Best,
> -Xiao
>
> On Thu, Jan 14, 2016 at 8:57 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> wrote:
>
>> Hi all,
>>
>> I've created an updated release candidate RC2 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/
>>
>> The RC tag in git is: release-2.7.2-RC2
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1027 <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1027>
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/releasenotes.html <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html> for
>> your quick perusal.
>>
>> As you may have noted,
>>   - I terminated the RC1 related voting thread after finding out that we
>> didn’t have a bunch of patches that are already in the released 2.6.3
>> version. After a brief discussion, we decided to keep the parallel 2.6.x
>> and 2.7.x releases incremental, see [4] for this discussion.
>>   - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>>   - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc <
>> http://markmail.org/message/5txhvr2qdiqglrwc>
>> [4] Retracted [VOTE] Release Apache Hadoop 2.7.2 RC1:
>> http://markmail.org/thread/n7ljbsnquihn3wlw
>


Mime
View raw message