You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by Wangda Tan <wh...@gmail.com> on 2016/06/07 05:50:22 UTC
Cannot create release artifacts for branch-2.8
Hi Hadoop Devs,
As you know, we're pushing 2.8.0 releases recently, there're couple of
issues that block creating release artifacts from source code.
I tried following approaches:
1) Run build through Hadoop Jenkins Job:
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
2) Run dev-support/create-release.sh
There're at most two issues cause the problem from what I can see:
1) https://issues.apache.org/jira/browse/HADOOP-12022 removed
releasenotes.html
2) https://issues.apache.org/jira/browse/HADOOP-11792 removed all
CHANGES.txt
I have tried to revert HADOOP-12022/HADOOP-11792 locally in branch-2.8,
create-releases.sh can run through and generate docs/artifacts correctly
(at least layout looks correctly, I haven't verified generated bits).
To make sure releases are not blocked, we have a couple of options:
a. Fix HADOOP-12892 and related issues, which requires to backport a couple
of commits which marked to be incompatible.
b. Revert both of the commits, and manual fix CHANGES.txt.
Any helps/suggestions are welcome.
Thanks,
Wangda
Re: Cannot create release artifacts for branch-2.8
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 for fixing create-release. I'll try to backport HADOOP-12892.
Thanks,
Akira
On 6/8/16 07:05, Wangda Tan wrote:
> It's also the best option to fix create-release. If we cannot get help to
> fix the script, it seems the only choice is to maintain CHANGES.txt again
> in branch-2.
>
> On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I'm not super happy about the alternative of reverting the auto-generated
>> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
>> again in branch-2. That's an overhead that we pay for every commit, and
>> it's particularly bad when doing backports.
>>
>> As I commented on HADOOP-12892, I think the backport should be possible,
>> and hopefully without backporting all the conflicting JIRAs. Maybe another
>> bash-savvy contributor could attempt it?
>>
>>
>>
>> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>>
>>>>
>>>> I'm not the one who cherry-picked them into branch-2, so I don't
>>>> care either way. I've been extremely open about targeting my code for
>>> the
>>>> past three years for trunk. With few exceptions, I generally only commit
>>>> code I write or even review to branch-2 if someone practically begs me.
>>>> That branch needs to die. Given my current situation, I'm certainly not
>>>> going to spend any unpaid time on it.
>>>
>>>
>>> Yeah, we all knew your preferences about this, you have the choice to work
>>> on whatever branch you like. :)
>>>
>>> Actually this question is to Andrew and Akira, I want to get consensus on
>>> this.
>>>
>>> Thanks,
>>> Wangda
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 for fixing create-release. I'll try to backport HADOOP-12892.
Thanks,
Akira
On 6/8/16 07:05, Wangda Tan wrote:
> It's also the best option to fix create-release. If we cannot get help to
> fix the script, it seems the only choice is to maintain CHANGES.txt again
> in branch-2.
>
> On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I'm not super happy about the alternative of reverting the auto-generated
>> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
>> again in branch-2. That's an overhead that we pay for every commit, and
>> it's particularly bad when doing backports.
>>
>> As I commented on HADOOP-12892, I think the backport should be possible,
>> and hopefully without backporting all the conflicting JIRAs. Maybe another
>> bash-savvy contributor could attempt it?
>>
>>
>>
>> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>>
>>>>
>>>> I'm not the one who cherry-picked them into branch-2, so I don't
>>>> care either way. I've been extremely open about targeting my code for
>>> the
>>>> past three years for trunk. With few exceptions, I generally only commit
>>>> code I write or even review to branch-2 if someone practically begs me.
>>>> That branch needs to die. Given my current situation, I'm certainly not
>>>> going to spend any unpaid time on it.
>>>
>>>
>>> Yeah, we all knew your preferences about this, you have the choice to work
>>> on whatever branch you like. :)
>>>
>>> Actually this question is to Andrew and Akira, I want to get consensus on
>>> this.
>>>
>>> Thanks,
>>> Wangda
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 for fixing create-release. I'll try to backport HADOOP-12892.
Thanks,
Akira
On 6/8/16 07:05, Wangda Tan wrote:
> It's also the best option to fix create-release. If we cannot get help to
> fix the script, it seems the only choice is to maintain CHANGES.txt again
> in branch-2.
>
> On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I'm not super happy about the alternative of reverting the auto-generated
>> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
>> again in branch-2. That's an overhead that we pay for every commit, and
>> it's particularly bad when doing backports.
>>
>> As I commented on HADOOP-12892, I think the backport should be possible,
>> and hopefully without backporting all the conflicting JIRAs. Maybe another
>> bash-savvy contributor could attempt it?
>>
>>
>>
>> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>>
>>>>
>>>> I'm not the one who cherry-picked them into branch-2, so I don't
>>>> care either way. I've been extremely open about targeting my code for
>>> the
>>>> past three years for trunk. With few exceptions, I generally only commit
>>>> code I write or even review to branch-2 if someone practically begs me.
>>>> That branch needs to die. Given my current situation, I'm certainly not
>>>> going to spend any unpaid time on it.
>>>
>>>
>>> Yeah, we all knew your preferences about this, you have the choice to work
>>> on whatever branch you like. :)
>>>
>>> Actually this question is to Andrew and Akira, I want to get consensus on
>>> this.
>>>
>>> Thanks,
>>> Wangda
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
It's also the best option to fix create-release. If we cannot get help to
fix the script, it seems the only choice is to maintain CHANGES.txt again
in branch-2.
On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
wrote:
> I'm not super happy about the alternative of reverting the auto-generated
> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
> again in branch-2. That's an overhead that we pay for every commit, and
> it's particularly bad when doing backports.
>
> As I commented on HADOOP-12892, I think the backport should be possible,
> and hopefully without backporting all the conflicting JIRAs. Maybe another
> bash-savvy contributor could attempt it?
>
>
>
> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>
>> >
>> > I'm not the one who cherry-picked them into branch-2, so I don't
>> > care either way. I've been extremely open about targeting my code for
>> the
>> > past three years for trunk. With few exceptions, I generally only commit
>> > code I write or even review to branch-2 if someone practically begs me.
>> > That branch needs to die. Given my current situation, I'm certainly not
>> > going to spend any unpaid time on it.
>>
>>
>> Yeah, we all knew your preferences about this, you have the choice to work
>> on whatever branch you like. :)
>>
>> Actually this question is to Andrew and Akira, I want to get consensus on
>> this.
>>
>> Thanks,
>> Wangda
>>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
It's also the best option to fix create-release. If we cannot get help to
fix the script, it seems the only choice is to maintain CHANGES.txt again
in branch-2.
On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
wrote:
> I'm not super happy about the alternative of reverting the auto-generated
> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
> again in branch-2. That's an overhead that we pay for every commit, and
> it's particularly bad when doing backports.
>
> As I commented on HADOOP-12892, I think the backport should be possible,
> and hopefully without backporting all the conflicting JIRAs. Maybe another
> bash-savvy contributor could attempt it?
>
>
>
> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>
>> >
>> > I'm not the one who cherry-picked them into branch-2, so I don't
>> > care either way. I've been extremely open about targeting my code for
>> the
>> > past three years for trunk. With few exceptions, I generally only commit
>> > code I write or even review to branch-2 if someone practically begs me.
>> > That branch needs to die. Given my current situation, I'm certainly not
>> > going to spend any unpaid time on it.
>>
>>
>> Yeah, we all knew your preferences about this, you have the choice to work
>> on whatever branch you like. :)
>>
>> Actually this question is to Andrew and Akira, I want to get consensus on
>> this.
>>
>> Thanks,
>> Wangda
>>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
It's also the best option to fix create-release. If we cannot get help to
fix the script, it seems the only choice is to maintain CHANGES.txt again
in branch-2.
On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang <an...@cloudera.com>
wrote:
> I'm not super happy about the alternative of reverting the auto-generated
> CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
> again in branch-2. That's an overhead that we pay for every commit, and
> it's particularly bad when doing backports.
>
> As I commented on HADOOP-12892, I think the backport should be possible,
> and hopefully without backporting all the conflicting JIRAs. Maybe another
> bash-savvy contributor could attempt it?
>
>
>
> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
>
>> >
>> > I'm not the one who cherry-picked them into branch-2, so I don't
>> > care either way. I've been extremely open about targeting my code for
>> the
>> > past three years for trunk. With few exceptions, I generally only commit
>> > code I write or even review to branch-2 if someone practically begs me.
>> > That branch needs to die. Given my current situation, I'm certainly not
>> > going to spend any unpaid time on it.
>>
>>
>> Yeah, we all knew your preferences about this, you have the choice to work
>> on whatever branch you like. :)
>>
>> Actually this question is to Andrew and Akira, I want to get consensus on
>> this.
>>
>> Thanks,
>> Wangda
>>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Andrew Wang <an...@cloudera.com>.
I'm not super happy about the alternative of reverting the auto-generated
CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
again in branch-2. That's an overhead that we pay for every commit, and
it's particularly bad when doing backports.
As I commented on HADOOP-12892, I think the backport should be possible,
and hopefully without backporting all the conflicting JIRAs. Maybe another
bash-savvy contributor could attempt it?
On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I'm not the one who cherry-picked them into branch-2, so I don't
> > care either way. I've been extremely open about targeting my code for
> the
> > past three years for trunk. With few exceptions, I generally only commit
> > code I write or even review to branch-2 if someone practically begs me.
> > That branch needs to die. Given my current situation, I'm certainly not
> > going to spend any unpaid time on it.
>
>
> Yeah, we all knew your preferences about this, you have the choice to work
> on whatever branch you like. :)
>
> Actually this question is to Andrew and Akira, I want to get consensus on
> this.
>
> Thanks,
> Wangda
>
Re: Cannot create release artifacts for branch-2.8
Posted by Andrew Wang <an...@cloudera.com>.
I'm not super happy about the alternative of reverting the auto-generated
CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
again in branch-2. That's an overhead that we pay for every commit, and
it's particularly bad when doing backports.
As I commented on HADOOP-12892, I think the backport should be possible,
and hopefully without backporting all the conflicting JIRAs. Maybe another
bash-savvy contributor could attempt it?
On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I'm not the one who cherry-picked them into branch-2, so I don't
> > care either way. I've been extremely open about targeting my code for
> the
> > past three years for trunk. With few exceptions, I generally only commit
> > code I write or even review to branch-2 if someone practically begs me.
> > That branch needs to die. Given my current situation, I'm certainly not
> > going to spend any unpaid time on it.
>
>
> Yeah, we all knew your preferences about this, you have the choice to work
> on whatever branch you like. :)
>
> Actually this question is to Andrew and Akira, I want to get consensus on
> this.
>
> Thanks,
> Wangda
>
Re: Cannot create release artifacts for branch-2.8
Posted by Andrew Wang <an...@cloudera.com>.
I'm not super happy about the alternative of reverting the auto-generated
CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance
again in branch-2. That's an overhead that we pay for every commit, and
it's particularly bad when doing backports.
As I commented on HADOOP-12892, I think the backport should be possible,
and hopefully without backporting all the conflicting JIRAs. Maybe another
bash-savvy contributor could attempt it?
On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I'm not the one who cherry-picked them into branch-2, so I don't
> > care either way. I've been extremely open about targeting my code for
> the
> > past three years for trunk. With few exceptions, I generally only commit
> > code I write or even review to branch-2 if someone practically begs me.
> > That branch needs to die. Given my current situation, I'm certainly not
> > going to spend any unpaid time on it.
>
>
> Yeah, we all knew your preferences about this, you have the choice to work
> on whatever branch you like. :)
>
> Actually this question is to Andrew and Akira, I want to get consensus on
> this.
>
> Thanks,
> Wangda
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
>
> I'm not the one who cherry-picked them into branch-2, so I don't
> care either way. I've been extremely open about targeting my code for the
> past three years for trunk. With few exceptions, I generally only commit
> code I write or even review to branch-2 if someone practically begs me.
> That branch needs to die. Given my current situation, I'm certainly not
> going to spend any unpaid time on it.
Yeah, we all knew your preferences about this, you have the choice to work
on whatever branch you like. :)
Actually this question is to Andrew and Akira, I want to get consensus on
this.
Thanks,
Wangda
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
>
> I'm not the one who cherry-picked them into branch-2, so I don't
> care either way. I've been extremely open about targeting my code for the
> past three years for trunk. With few exceptions, I generally only commit
> code I write or even review to branch-2 if someone practically begs me.
> That branch needs to die. Given my current situation, I'm certainly not
> going to spend any unpaid time on it.
Yeah, we all knew your preferences about this, you have the choice to work
on whatever branch you like. :)
Actually this question is to Andrew and Akira, I want to get consensus on
this.
Thanks,
Wangda
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
>
> I'm not the one who cherry-picked them into branch-2, so I don't
> care either way. I've been extremely open about targeting my code for the
> past three years for trunk. With few exceptions, I generally only commit
> code I write or even review to branch-2 if someone practically begs me.
> That branch needs to die. Given my current situation, I'm certainly not
> going to spend any unpaid time on it.
Yeah, we all knew your preferences about this, you have the choice to work
on whatever branch you like. :)
Actually this question is to Andrew and Akira, I want to get consensus on
this.
Thanks,
Wangda
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <aw...@apache.org>.
> On Jun 7, 2016, at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> That gonna be very helpful, but I guess it only works on trunk, correct? At
> least many of the parameters you mentioned are not in create-release.sh of
> branch-2.
Yup. create-release was rewritten in trunk. The previous version had some interesting race conditions and other problems that made any releases built from it highly suspect. (never mind the whole 'against ASF policy' problem when run on Jenkins)
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
I'm not the one who cherry-picked them into branch-2, so I don't care either way. I've been extremely open about targeting my code for the past three years for trunk. With few exceptions, I generally only commit code I write or even review to branch-2 if someone practically begs me. That branch needs to die. Given my current situation, I'm certainly not going to spend any unpaid time on it.
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
+ Andrew/Akira
On Tue, Jun 7, 2016 at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
> That gonna be very helpful, but I guess it only works on trunk, correct?
> At least many of the parameters you mentioned are not in create-release.sh
> of branch-2.
>
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
>
> + Andrew/Akira who backported the two patches to branch-2, is it safe to
> revert the two patches? Are there any other dependency patches I need to
> take care?
>
> Thanks,
> Wangda
>
>
> On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
> allenwittenauer@yahoo.com.invalid> wrote:
>
>>
>> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>> >
>> > I have tested both, create-releases fails on my local box as well.
>> >
>> > According to the link you provided, we probably need to update how to
>> > release wiki
>> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>>
>>
>> I'm working on writing directions on how to use
>> dev-support/bin/create-release for an ASF release. But short directions:
>>
>> * need a working .gpg directory
>> * use --asfrelease
>> * use --docker and --dockercache on Linux
>> * after vote passes, commit the generated release documentation
>> back to the various branches
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <aw...@apache.org>.
> On Jun 7, 2016, at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> That gonna be very helpful, but I guess it only works on trunk, correct? At
> least many of the parameters you mentioned are not in create-release.sh of
> branch-2.
Yup. create-release was rewritten in trunk. The previous version had some interesting race conditions and other problems that made any releases built from it highly suspect. (never mind the whole 'against ASF policy' problem when run on Jenkins)
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
I'm not the one who cherry-picked them into branch-2, so I don't care either way. I've been extremely open about targeting my code for the past three years for trunk. With few exceptions, I generally only commit code I write or even review to branch-2 if someone practically begs me. That branch needs to die. Given my current situation, I'm certainly not going to spend any unpaid time on it.
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
+ Andrew/Akira
On Tue, Jun 7, 2016 at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
> That gonna be very helpful, but I guess it only works on trunk, correct?
> At least many of the parameters you mentioned are not in create-release.sh
> of branch-2.
>
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
>
> + Andrew/Akira who backported the two patches to branch-2, is it safe to
> revert the two patches? Are there any other dependency patches I need to
> take care?
>
> Thanks,
> Wangda
>
>
> On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
> allenwittenauer@yahoo.com.invalid> wrote:
>
>>
>> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>> >
>> > I have tested both, create-releases fails on my local box as well.
>> >
>> > According to the link you provided, we probably need to update how to
>> > release wiki
>> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>>
>>
>> I'm working on writing directions on how to use
>> dev-support/bin/create-release for an ASF release. But short directions:
>>
>> * need a working .gpg directory
>> * use --asfrelease
>> * use --docker and --dockercache on Linux
>> * after vote passes, commit the generated release documentation
>> back to the various branches
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
+ Andrew/Akira
On Tue, Jun 7, 2016 at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
> That gonna be very helpful, but I guess it only works on trunk, correct?
> At least many of the parameters you mentioned are not in create-release.sh
> of branch-2.
>
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
>
> + Andrew/Akira who backported the two patches to branch-2, is it safe to
> revert the two patches? Are there any other dependency patches I need to
> take care?
>
> Thanks,
> Wangda
>
>
> On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
> allenwittenauer@yahoo.com.invalid> wrote:
>
>>
>> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>> >
>> > I have tested both, create-releases fails on my local box as well.
>> >
>> > According to the link you provided, we probably need to update how to
>> > release wiki
>> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>>
>>
>> I'm working on writing directions on how to use
>> dev-support/bin/create-release for an ASF release. But short directions:
>>
>> * need a working .gpg directory
>> * use --asfrelease
>> * use --docker and --dockercache on Linux
>> * after vote passes, commit the generated release documentation
>> back to the various branches
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <aw...@apache.org>.
> On Jun 7, 2016, at 1:44 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> That gonna be very helpful, but I guess it only works on trunk, correct? At
> least many of the parameters you mentioned are not in create-release.sh of
> branch-2.
Yup. create-release was rewritten in trunk. The previous version had some interesting race conditions and other problems that made any releases built from it highly suspect. (never mind the whole 'against ASF policy' problem when run on Jenkins)
> We may need to make a decision for this in branch-2. Honestly, I have
> little understanding about shell script related stuffs, if I cannot get
> help about fixing create-release.sh, I would prefer to revert both of
> HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
> manually.
>
> Would like to hear your thoughts.
I'm not the one who cherry-picked them into branch-2, so I don't care either way. I've been extremely open about targeting my code for the past three years for trunk. With few exceptions, I generally only commit code I write or even review to branch-2 if someone practically begs me. That branch needs to die. Given my current situation, I'm certainly not going to spend any unpaid time on it.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
That gonna be very helpful, but I guess it only works on trunk, correct? At
least many of the parameters you mentioned are not in create-release.sh of
branch-2.
We may need to make a decision for this in branch-2. Honestly, I have
little understanding about shell script related stuffs, if I cannot get
help about fixing create-release.sh, I would prefer to revert both of
HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
manually.
Would like to hear your thoughts.
+ Andrew/Akira who backported the two patches to branch-2, is it safe to
revert the two patches? Are there any other dependency patches I need to
take care?
Thanks,
Wangda
On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
allenwittenauer@yahoo.com.invalid> wrote:
>
> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I have tested both, create-releases fails on my local box as well.
> >
> > According to the link you provided, we probably need to update how to
> > release wiki
> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>
>
> I'm working on writing directions on how to use
> dev-support/bin/create-release for an ASF release. But short directions:
>
> * need a working .gpg directory
> * use --asfrelease
> * use --docker and --dockercache on Linux
> * after vote passes, commit the generated release documentation
> back to the various branches
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
That gonna be very helpful, but I guess it only works on trunk, correct? At
least many of the parameters you mentioned are not in create-release.sh of
branch-2.
We may need to make a decision for this in branch-2. Honestly, I have
little understanding about shell script related stuffs, if I cannot get
help about fixing create-release.sh, I would prefer to revert both of
HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
manually.
Would like to hear your thoughts.
+ Andrew/Akira who backported the two patches to branch-2, is it safe to
revert the two patches? Are there any other dependency patches I need to
take care?
Thanks,
Wangda
On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
allenwittenauer@yahoo.com.invalid> wrote:
>
> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I have tested both, create-releases fails on my local box as well.
> >
> > According to the link you provided, we probably need to update how to
> > release wiki
> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>
>
> I'm working on writing directions on how to use
> dev-support/bin/create-release for an ASF release. But short directions:
>
> * need a working .gpg directory
> * use --asfrelease
> * use --docker and --dockercache on Linux
> * after vote passes, commit the generated release documentation
> back to the various branches
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
That gonna be very helpful, but I guess it only works on trunk, correct? At
least many of the parameters you mentioned are not in create-release.sh of
branch-2.
We may need to make a decision for this in branch-2. Honestly, I have
little understanding about shell script related stuffs, if I cannot get
help about fixing create-release.sh, I would prefer to revert both of
HADOOP-12022/HADOOP-11792 from branch-2/branch-2.8 and adding CHANGES.txt
manually.
Would like to hear your thoughts.
+ Andrew/Akira who backported the two patches to branch-2, is it safe to
revert the two patches? Are there any other dependency patches I need to
take care?
Thanks,
Wangda
On Tue, Jun 7, 2016 at 11:45 AM, Allen Wittenauer <
allenwittenauer@yahoo.com.invalid> wrote:
>
> > On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > I have tested both, create-releases fails on my local box as well.
> >
> > According to the link you provided, we probably need to update how to
> > release wiki
> > <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
>
>
> I'm working on writing directions on how to use
> dev-support/bin/create-release for an ASF release. But short directions:
>
> * need a working .gpg directory
> * use --asfrelease
> * use --docker and --dockercache on Linux
> * after vote passes, commit the generated release documentation
> back to the various branches
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>
> I have tested both, create-releases fails on my local box as well.
>
> According to the link you provided, we probably need to update how to
> release wiki
> <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
I'm working on writing directions on how to use dev-support/bin/create-release for an ASF release. But short directions:
* need a working .gpg directory
* use --asfrelease
* use --docker and --dockercache on Linux
* after vote passes, commit the generated release documentation back to the various branches
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>
> I have tested both, create-releases fails on my local box as well.
>
> According to the link you provided, we probably need to update how to
> release wiki
> <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
I'm working on writing directions on how to use dev-support/bin/create-release for an ASF release. But short directions:
* need a working .gpg directory
* use --asfrelease
* use --docker and --dockercache on Linux
* after vote passes, commit the generated release documentation back to the various branches
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 7, 2016, at 11:37 AM, Wangda Tan <wh...@gmail.com> wrote:
>
> I have tested both, create-releases fails on my local box as well.
>
> According to the link you provided, we probably need to update how to
> release wiki
> <http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
I'm working on writing directions on how to use dev-support/bin/create-release for an ASF release. But short directions:
* need a working .gpg directory
* use --asfrelease
* use --docker and --dockercache on Linux
* after vote passes, commit the generated release documentation back to the various branches
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
I have tested both, create-releases fails on my local box as well.
According to the link you provided, we probably need to update how to
release wiki
<http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
On Tue, Jun 7, 2016 at 6:22 AM, Allen Wittenauer <al...@yahoo.com>
wrote:
>
> > On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > Hi Hadoop Devs,
> >
> > As you know, we're pushing 2.8.0 releases recently, there're couple of
> > issues that block creating release artifacts from source code.
> >
> > I tried following approaches:
> > 1) Run build through Hadoop Jenkins Job:
>
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
I have tested both, create-releases fails on my local box as well.
According to the link you provided, we probably need to update how to
release wiki
<http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
On Tue, Jun 7, 2016 at 6:22 AM, Allen Wittenauer <al...@yahoo.com>
wrote:
>
> > On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > Hi Hadoop Devs,
> >
> > As you know, we're pushing 2.8.0 releases recently, there're couple of
> > issues that block creating release artifacts from source code.
> >
> > I tried following approaches:
> > 1) Run build through Hadoop Jenkins Job:
>
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Wangda Tan <wh...@gmail.com>.
I have tested both, create-releases fails on my local box as well.
According to the link you provided, we probably need to update how to
release wiki
<http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=81>.
On Tue, Jun 7, 2016 at 6:22 AM, Allen Wittenauer <al...@yahoo.com>
wrote:
>
> > On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
> >
> > Hi Hadoop Devs,
> >
> > As you know, we're pushing 2.8.0 releases recently, there're couple of
> > issues that block creating release artifacts from source code.
> >
> > I tried following approaches:
> > 1) Run build through Hadoop Jenkins Job:
>
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
>
>
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> Hi Hadoop Devs,
>
> As you know, we're pushing 2.8.0 releases recently, there're couple of
> issues that block creating release artifacts from source code.
>
> I tried following approaches:
> 1) Run build through Hadoop Jenkins Job:
http://www.apache.org/dev/release.html#owned-controlled-hardware
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> Hi Hadoop Devs,
>
> As you know, we're pushing 2.8.0 releases recently, there're couple of
> issues that block creating release artifacts from source code.
>
> I tried following approaches:
> 1) Run build through Hadoop Jenkins Job:
http://www.apache.org/dev/release.html#owned-controlled-hardware
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: Cannot create release artifacts for branch-2.8
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Jun 6, 2016, at 10:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> Hi Hadoop Devs,
>
> As you know, we're pushing 2.8.0 releases recently, there're couple of
> issues that block creating release artifacts from source code.
>
> I tried following approaches:
> 1) Run build through Hadoop Jenkins Job:
http://www.apache.org/dev/release.html#owned-controlled-hardware
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org