Done.
- Tsuyoshi
On Wed, Oct 21, 2015 at 8:53 PM, Tsuyoshi Ozawa wrote:
> Thanks for your notification, Sangjin. I'll backport YARN-3798 soon.
>
> - Tsuyoshi
>
> On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote:
>> If you have backported bugfixes to 2.7.2, please take a moment to consider
>>
Thanks for your notification, Sangjin. I'll backport YARN-3798 soon.
- Tsuyoshi
On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote:
> If you have backported bugfixes to 2.7.2, please take a moment to consider
> if it is relevant (and important) for 2.6.x too, and if so backport it to
> branch-2
If you have backported bugfixes to 2.7.2, please take a moment to consider
if it is relevant (and important) for 2.6.x too, and if so backport it to
branch-2.6. Thanks!
On Tue, Oct 20, 2015 at 9:33 AM, Sangjin Lee wrote:
> Another friendly reminder that I'll be cutting the branch and creating th
Another friendly reminder that I'll be cutting the branch and creating the
RC soon. I'm targeting tomorrow. Thanks!
Sangjin
On Mon, Oct 12, 2015 at 11:40 AM, Sangjin Lee wrote:
> Hi all,
>
> We are targeting next week to create the first RC for 2.6.2. Currently
> there are 14 issues that are co
Hi all,
We are targeting next week to create the first RC for 2.6.2. Currently
there are 14 issues that are committed to branch-2.6. If you have bug fixes
that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x
and would improve the quality of those releases, please take time to
Thanks Sangjin.
-Vinay
On Sat, Sep 26, 2015 at 9:49 PM, Sangjin Lee wrote:
> I have updated branch-2.6 and force pushed the branch. I checked the branch
> out from scratch and tested building it.
>
> Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check
> if it applies clea
I have updated branch-2.6 and force pushed the branch. I checked the branch
out from scratch and tested building it.
Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check
if it applies cleanly before committing to branch-2.6.
Thanks,
Sangjin
On Fri, Sep 25, 2015 at 4:42 PM,
Per Vinod's suggestion, in order to reduce the amount of movement I'll pick
commits from branch-2.6 onto the tip of branch-2.6.1 rather than the other
way around. This means I'll need to move branch-2.6 and force push that
change.
Could you please hold off on committing to branch-2.6 until I am do
Thanks folks. I'll get started on the items Vinod mentioned soon.
If you have something you'd like to push for inclusion in 2.6.2, please
mark the target version as 2.6.2.
I'd like to ask one more thing on top of that. It would be AWESOME if you
can check if it can be applied cleanly on top of 2.
Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for
2.6.2!
+1. If there's anything I can help you with, please tell me.
Thanks,
Akira
On 9/25/15 13:23, Vinayakumar B wrote:
Thanks Vinod and Sangjin for making 2.6.1 release possible.
Apologies for not getting time to veri
Thanks Vinod and Sangjin for making 2.6.1 release possible.
Apologies for not getting time to verify and vote for the release.
I will also be available to help for 2.6.2 if anything required.
Thanks,
Vinay
On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli wrote:
> +1. Please take it over, I
+1. Please take it over, I’ll standby for any help needed.
Thanks
+Vinod
On Sep 24, 2015, at 11:34 AM, Sangjin Lee
mailto:sj...@apache.org>> wrote:
I'd like to volunteer as the release manager for 2.6.2 unless there is an
objection.
Thanks Vinod for starting the discussion for 2.6.2!
I'd like to volunteer as the release manager for 2.6.2 unless there is an
objection. As I've worked with Vinod and Akira for 2.6.1 and triaged a
number of issues, I feel I should be in a good position to take care of
2.6.2. Let me know your thoug
13 matches
Mail list logo
