;
> Hi Konstantin Shvachko
>
>
>
> how about creating a wiki page for 2.7.4 release status like 2.8 and
> trunk in following link.??
>
>
> https://cwiki.apache.org/confluence/display/HADOOP
>
>
>
> From: Konstantin Shvachko <shv.had...@gmail
ested in Dynamometer. Erik (CC-ed) is actively working
>> on this project right now, I'll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open sour
ad you are interested in Dynamometer. Erik (CC-ed) is actively working
>> on this project right now, I'll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open s
luence/display/HADOOP/Hadoop+2.7.4
>>>>>
>>>>> If you want to edit this wiki, please ping me.
>>>>>
>>>>> Regards,
>>>>> Akira
>>>>>
>>>>>
>>>>> On 2017/05/
is actively working
>> on this project right now, I'll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open source
>> it. You can fork the "About 2.7.4 Rele
wiki, please ping me.
>>>>
>>>> Regards,
>>>> Akira
>>>>
>>>>
>>>> On 2017/05/23 4:42, Brahma Reddy Battula wrote:
>>>>
>>>> Hi Konstantin Shvachko
>>>>>
>>>>>
>>>>> how about creating a wiki page
:
>>>
>>> Hi Konstantin Shvachko
>>>>
>>>>
>>>> how about creating a wiki page for 2.7.4 release status like 2.8 and
>>>> trunk in following link.??
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/HADOOP
>>>
he.org;
yarn-dev@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Latest update on the links and filters. Here is the correct link for the
filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?
requestId=12340814
Also updated: https://s.apache.org/Dzg4
Had to do some Jira debugging. Sor
owing link.??
>>
>>
>> https://cwiki.apache.org/confluence/display/HADOOP
>>
>>
>>
>> From: Konstantin Shvachko <shv.had...@gmail.com>
>> Sent: Saturday, May 13, 2017 3:58 AM
>> To: Akira Ajisaka
>> Cc: Hadoop Common; Hd
rn-dev@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Latest update on the links and filters. Here is the correct link for the
filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12340814
Also updated: https://s.apache.org/Dzg4
Had to do some Jira debugging.
:58 AM
To: Akira Ajisaka
Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-dev@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Latest update on the links and filters. Here is the correct link for the
filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12
t;>>
>>>> https://issues.apache.org/jira/browse/HDFS-9311===Life Line Protocol
>>>> https://issues.apache.org/jira/browse/HDFS-10987===Deecommission
>>>> Expensive when lot's of blocks are present
>>>>
>>>> https://issues.apache.org/jira/bro
://issues.apache.org/jira/browse/HDFS-8312===Trash does not descent
>>> into child directories to check for permission
>>> https://issues.apache.org/jira/browse/HADOOP-14100===Upgrade Jsch jar to
>>> latest version to fix vulnerability in old versions
>>>
>>>
ersion to fix vulnerability in old versions
>
>
>
> Regards
> Brahma Reddy Battula
>
> -Original Message-
> From: Erik Krogen [mailto:ekro...@linkedin.com.INVALID]
> Sent: 06 May 2017 02:40
> To: Konstantin Shvachko
> Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; mapreduce-
ailto:ekro...@linkedin.com.INVALID]
Sent: 06 May 2017 02:40
To: Konstantin Shvachko
Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-dev@hadoop.apache.org
Subject: Re: About 2.7.4 Release
List LGTM Konstantin!
Let's say that we will only create a new tracking JIRA f
Great Zhe. Let's monitor the build.
I marked all jiras I knew of for inclusion into 2.7.4 as I described before.
Target Version/s: 2.7.4
Label: release-blocker
Here is the link to the list: https://s.apache.org/Dzg4
Please let me know if I missed anything.
And feel free to pick up any. Most of
Thanks for volunteering as RM Konstantin! The plan LGTM.
I've created a nightly Jenkins job for branch-2.7 (unit tests):
https://builds.apache.org/job/Hadoop-branch2.7-nightly/
On Wed, May 3, 2017 at 12:42 AM Konstantin Shvachko
wrote:
> Hey guys,
>
> I and a few of my
Hey guys,
I and a few of my colleagues would like to help here and move 2.7.4 release
forward. A few points in this regard.
1. Reading through this thread since March 1 I see that Vinod hinted on
managing the release. Vinod, if you still want the job / have bandwidth
will be happy to work with
Can we wait for 2.7.4 first? There are still backports happening to
branch-2.7. After that, there shouldn't be many backports since both 2.8.x
and 2.7.x will be up-to-date with what's in 3.0.0-alpha1 and 3.0.0-alpha2.
On Tue, May 2, 2017 at 4:07 PM, Allen Wittenauer
Is there any reason to not Close -alpha1+resolved state JIRAs? It's been quite
a while and those definitely should not getting re-opened anymore. What about
-alpha2's that are also resolved?
-
To unsubscribe, e-mail:
On Mon, May 1, 2017 at 3:44 PM, Allen Wittenauer
wrote:
>
> > On May 1, 2017, at 2:27 PM, Andrew Wang
> wrote:
> > I believe I asked about this on dev-yetus a while back. I'd prefer that
> the presence of the fix version be sufficient to
> On May 1, 2017, at 2:27 PM, Andrew Wang wrote:
> I believe I asked about this on dev-yetus a while back. I'd prefer that the
> presence of the fix version be sufficient to indicate whether a JIRA is
> included in a release branch. Yetus requires that the JIRA be
I didn't close JIRAs after the 3.0.0-alpha1 or alpha2 releases since
closing makes the JIRAs read-only. This makes it more annoying to backport
to older releases and for concurrent releases in general.
I believe I asked about this on dev-yetus a while back. I'd prefer that the
presence of the fix
Thanks Allen for the additional information.
> At one point, JIRA was configured to refuse re-opening after a
release is cut.
In the past, release manager closed the tickets and the process is
written in the wiki: https://wiki.apache.org/hadoop/HowToRelease
> 10. In JIRA, close issues
> On Apr 25, 2017, at 12:35 AM, Akira Ajisaka wrote:
> > Maybe we should create a jira to track this?
>
> I think now either way (reopen or create) is fine.
>
> Release doc maker creates change logs by fetching information from JIRA, so
> reopening the tickets should be
; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
> It would be great to backport HDFS-9710 to 2.7.4 as this is one of the >
critical fixes on scalability.
Sounds good.
> Maybe we should create a jira to track this?
I think n
Ajisaka [mailto:aajis...@apache.org]
Sent: 25 April 2017 15:36
To: Haohui Mai
Cc: Brahma Reddy Battula; Andrew Wang; Sangjin Lee; Vinod Kumar Vavilapalli;
Marton Elek; Hadoop Common; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
> It wo
mailto:andrew.w...@cloudera.com]
Sent: 08 March 2017 04:22
To: Sangjin Lee
Cc: Marton Elek; Hadoop Common; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the wiki:
2.6/2.7:
https://wiki.apache.org/hadoop/HowTo
I can
>> help on this..
>>
>>
>>
>> Regards
>> Brahma Reddy Battula
>>
>> -Original Message-
>> From: Andrew Wang [mailto:andrew.w...@cloudera.com]
>> Sent: 08 March 2017 04:22
>> To: Sangjin Lee
>> Cc: Marton Elek; Had
-Original Message-
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: 08 March 2017 04:22
To: Sangjin Lee
Cc: Marton Elek; Hadoop Common; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the wiki
@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the wiki:
2.6/2.7:
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
2.8+:
https://wiki.apache.org/hadoop/HowToRelease
I think given the push toward 2.8 and 3.0, there's
> On Mar 8, 2017, at 1:54 PM, Allen Wittenauer
> wrote:
>
> This is already possible:
> * don’t use —asfrelease
> * use —sign, —native, and, if appropriate for your platform,
> —docker and —dockercache
Oh yeah, I forgot
> On Mar 8, 2017, at 10:55 AM, Marton Elek wrote:
>
> I think the main point here is the testing of the release script, not the
> creation of the official release.
… except the Hadoop PMC was doing exactly this from 2.3.0 up until
recently. Which means we have
w Wang
Cc: Hadoop Common; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
> On Mar 7, 2017, at 2:51 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
017 11:58 PM
To: Sangjin Lee
Cc: Marton Elek; common-...@hadoop.apache.org; yarn-dev@hadoop.apache.org;
Hdfs-dev; mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
I was planning to take this up, celebrating my return from my paternity leave
of absence for quite a while.
Marton,
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
Just a reminder that any such build cannot be used for an actual
release:
I was planning to take this up, celebrating my return from my paternity leave
of absence for quite a while.
Marton, let me know if you do want to take this up instead and we can work
together.
Thanks
+Vinod
> On Mar 7, 2017, at 9:13 AM, Sangjin Lee wrote:
>
> If we have a
> > release script, anything else) I would be happy to do any task for new
> > maintenance releases (or more frequent releases).
> >
> > Regards,
> > Marton
> >
> >
> >
> > From: Akira Ajisaka <aajis...@apache.org>
> > Sent: Tuesday,
aintenance releases (or more frequent releases).
>
> Regards,
> Marton
>
>
>
> From: Akira Ajisaka <aajis...@apache.org>
> Sent: Tuesday, March 07, 2017 7:34 AM
> To: Brahma Reddy Battula; Hadoop Common; yarn-dev@hadoop.apache.org;
> Hdfs-dev; mapreduce-
ds,
Marton
From: Akira Ajisaka <aajis...@apache.org>
Sent: Tuesday, March 07, 2017 7:34 AM
To: Brahma Reddy Battula; Hadoop Common; yarn-dev@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Probably 2.8.0 will
Probably 2.8.0 will be released soon.
https://issues.apache.org/jira/browse/HADOOP-13866?focusedCommentId=15898379=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15898379
I'm thinking 2.7.4 release process starts after 2.8.0 release,
so 2.7.4 will be released in April
Hi All
It has been six months for branch-2.7 release.. is there any near plan for
2.7.4..?
Thanks
Brahma Reddy Battula
42 matches
Mail list logo