I have done the change.
All committers,
2.8.2 release is supposed to be a stable/production release for
branch-2.8. For commits to go for 2.8.2 release (only important and low risk
bug fixes), please commit to trunk, branch-2, branch-2.8 and branch-2.8.2. For
unimportant or high risk bug fixes/improvements, please commit to branch-2.8
(trunk/branch-2) only and mark JIRA fixed as 2.8.3. Thanks for your cooperation!
Thanks,
Junping
________________________________
From: Junping Du
Sent: Monday, July 24, 2017 10:36 AM
To: Brahma Reddy Battula; Vinod Kumar Vavilapalli
Cc: Kihwal Lee; [email protected]; [email protected];
[email protected]; [email protected]; Jason Lowe;
[email protected]
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Nice catch, Brahma. Actually, this is not supposed to be happen as we all
should know the patch should firstly get landed on branch-2.8 (as well as
trunk, branch-2) before landed on branch-2.8.2. Anyway, we will always check
JIRAs claim to fixed in a specific release version with commits actually
landing on the releasing branch before kicking off RC. So, I am not too worry
about this mistaking behaviors as it happens in every releases.
If no other concerns, I will do the branch update in next 30 minutes.
Thanks,
Junping
________________________________
From: Brahma Reddy Battula <[email protected]>
Sent: Sunday, July 23, 2017 1:50 AM
To: Junping Du; Vinod Kumar Vavilapalli
Cc: Kihwal Lee; [email protected]; [email protected];
[email protected]; [email protected]; Jason Lowe;
[email protected]
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Just executed the "git log branch-2.8 ^branch-2.8.2" found two commits are
missed (HDFS-8312 and HADOOP-13867 ) in branch-2.8.I just pushed this two
commits.Hope we'll not miss any commits which present in only in branch-2.8.2.
________________________________
From: Junping Du <[email protected]>
Sent: Saturday, July 22, 2017 5:57 AM
To: Vinod Kumar Vavilapalli
Cc: Kihwal Lee; [email protected]; [email protected];
[email protected]; [email protected]; Jason Lowe;
[email protected]
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Already get back from Daniel who is from ASF INFRA team, I plan to do following
operations on next Monday morning:
1. Drop current branch-2.8.2 and recut branch-2.8.2 from branch-2.8
2. Drop abandoned branch-2.8.1 and rename branch-2.8.1-private to branch-2.8.1
where we just released 2.8.1 from.
I will also adjust fix version on all affected JIRA accordingly.
If you have any concerns on above operations, please raise it before the end of
this Sunday (7/23).
Thanks,
Junping
________________________________________
From: Junping Du <[email protected]>
Sent: Friday, July 21, 2017 2:29 PM
To: Vinod Kumar Vavilapalli
Cc: Kihwal Lee; [email protected]; [email protected];
[email protected]; [email protected]; Jason Lowe
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Make sense, just raise: https://issues.apache.org/jira/browse/INFRA-14669
Thanks,
Junping
________________________________________
From: Vinod Kumar Vavilapalli <[email protected]>
Sent: Friday, July 21, 2017 12:31 PM
To: Junping Du
Cc: Kihwal Lee; [email protected]; [email protected];
[email protected]; [email protected]; Jason Lowe
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Junping,
If we are looking at a month, I’d not rebranch branch-2.8.2 right now given how
these things go. We can just continue to commit on branch-2.8 for now.
I also think we should just follow up with ASF INFRA and clean up the branches
- Delete branch-2.8.2 so that we can recreate it afresh a little later.
- branch-2.8.1 is also stale and it should be deleted. branch-2.8.1-private
should be renamed to branch-2.8.1
Thanks
+Vinod
> On Jul 21, 2017, at 11:23 AM, Junping Du <[email protected]> wrote:
>
> Thanks for suggestions, Jason and Kihwal!
> +1 on releasing 2.8.2 on latest branch-2.8 too. Practically, if branch-2.8.2
> cannot be abandoned/replaced (suspect all branches are read-only now), I will
> manually merge all commits that not landed on 2.8.2 yet.
>
> Thanks,
>
> Junping
> ________________________________________
> From: Jason Lowe <[email protected]>
> Sent: Friday, July 21, 2017 8:17 AM
> To: Kihwal Lee; Junping Du; [email protected];
> [email protected]; [email protected];
> [email protected]
> Subject: Re: Apache Hadoop 2.8.2 Release Plan
>
> +1 to base the 2.8.2 release off of the more recent activity on branch-2.8.
> Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that
> are in branch-2.8. There also are a lot of JIRAs that claim they are fixed
> in 2.8.2 but are not in branch-2.8.2. Having the 2.8.2 release be based on
> recent activity in branch-2.8 would solve both of these issues, and we'd only
> need to move the handful of JIRAs that have marked themselves correctly as
> fixed in 2.8.3 to be fixed in 2.8.2.
>
> Jason
>
>
> On Friday, July 21, 2017 10:01 AM, Kihwal Lee
> <[email protected]> wrote:
>
>
> Thanks for driving the next 2.8 release, Junping. While I was committing a
> blocker for 2.7.4, I noticed some of the jiras are back-ported to 2.7, but
> missing in branch-2.8.2. Perhaps it is safer and easier to simply rebranch
> 2.8.2.
> Thanks,Kihwal
>
> On Thursday, July 20, 2017, 3:32:16 PM CDT, Junping Du <[email protected]>
> wrote:
>
> Hi all,
> Per Vinod's previous email, we just announce Apache Hadoop 2.8.1 get
> released today which is a special security release. Now, we should work
> towards 2.8.2 release which aim for production deployment. The focus
> obviously is to fix blocker/critical issues [2], bug-fixes and *no* features
> / improvements. We currently have 13 blocker/critical issues, and 10 of them
> are Patch Available.
>
> I plan to cut an RC in a month - target for releasing before end of Aug., to
> give enough time for outstanding blocker / critical issues. Will start moving
> out any tickets that are not blockers and/or won't fit the timeline. For
> progress of releasing effort, please refer our release wiki [2].
>
> Please share thoughts if you have any. Thanks!
>
> Thanks,
>
> Junping
>
> [1] 2.8.2 release Blockers/Criticals: https://s.apache.org/JM5x
> [2] 2.8 Release wiki:
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
Hadoop 2.8 Release - Hadoop - Apache Software
Foundation<https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release>
cwiki.apache.org
Release schedule. It has been over 1 year since last minor release 2.7.0, so we
plan to release Hadoop 2.8.0 as soon as we can. Per discussions on community
threads ...
>
> ________________________________________
> From: Vinod Kumar Vavilapalli <[email protected]>
> Sent: Thursday, July 20, 2017 1:05 PM
> To: [email protected]
> Subject: [ANNOUNCE] Apache Hadoop 2.8.1 is released
>
> Hi all,
>
> The Apache Hadoop PMC has released version 2.8.1. You can get it from this
> page: http://hadoop.apache.org/releases.html#Download
Apache Hadoop Releases<http://hadoop.apache.org/releases.html#Download>
hadoop.apache.org
To verify Hadoop releases using GPG: Download the release
hadoop-X.Y.Z-src.tar.gz from a mirror site. Download the signature file
hadoop-X.Y.Z-src.tar ...
> This is a security release in the 2.8.0 release line. It consists of 2.8.0
> plus security fixes. Users on 2.8.0 are encouraged to upgrade to 2.8.1.
>
> Please note that 2.8.x release line continues to be not yet ready for
> production use. Critical issues are being ironed out via testing and
> downstream adoption. Production users should wait for a subsequent release in
> the 2.8.x line.
>
> Thanks
> +Vinod
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
