You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by Andrew Wang <an...@cloudera.com> on 2016/03/04 06:11:17 UTC
CHANGES.txt is gone from trunk, branch-2, branch-2.8
Hi all,
With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
and release notes are now generated by Yetus. I've gone ahead and deleted
the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
(HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
and the Yetus integration.
I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
at a high-level, this means we no longer need to edit CHANGES.txt on new
commit, streamlining our commit process. CHANGES.txt updates will still be
necessary for backports to older release lines like 2.6.x and 2.7.x.
Happy committing!
Best,
Andrew
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by Ravi Prakash <ra...@gmail.com>.
Yaayy!! +1
On Tue, Mar 8, 2016 at 10:59 AM, Colin P. McCabe <cm...@apache.org> wrote:
> +1
>
> Thanks, Andrew. This will avoid so many spurious conflicts when
> cherry-picking changes, and so much wasted time on commit.
>
> best,
> Colin
>
> On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com>
> wrote:
> > Hi all,
> >
> > With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> > and release notes are now generated by Yetus. I've gone ahead and deleted
> > the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> > (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> > and the Yetus integration.
> >
> > I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> > at a high-level, this means we no longer need to edit CHANGES.txt on new
> > commit, streamlining our commit process. CHANGES.txt updates will still
> be
> > necessary for backports to older release lines like 2.6.x and 2.7.x.
> >
> > Happy committing!
> >
> > Best,
> > Andrew
>
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by Ravi Prakash <ra...@gmail.com>.
Yaayy!! +1
On Tue, Mar 8, 2016 at 10:59 AM, Colin P. McCabe <cm...@apache.org> wrote:
> +1
>
> Thanks, Andrew. This will avoid so many spurious conflicts when
> cherry-picking changes, and so much wasted time on commit.
>
> best,
> Colin
>
> On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com>
> wrote:
> > Hi all,
> >
> > With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> > and release notes are now generated by Yetus. I've gone ahead and deleted
> > the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> > (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> > and the Yetus integration.
> >
> > I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> > at a high-level, this means we no longer need to edit CHANGES.txt on new
> > commit, streamlining our commit process. CHANGES.txt updates will still
> be
> > necessary for backports to older release lines like 2.6.x and 2.7.x.
> >
> > Happy committing!
> >
> > Best,
> > Andrew
>
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by Ravi Prakash <ra...@gmail.com>.
Yaayy!! +1
On Tue, Mar 8, 2016 at 10:59 AM, Colin P. McCabe <cm...@apache.org> wrote:
> +1
>
> Thanks, Andrew. This will avoid so many spurious conflicts when
> cherry-picking changes, and so much wasted time on commit.
>
> best,
> Colin
>
> On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com>
> wrote:
> > Hi all,
> >
> > With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> > and release notes are now generated by Yetus. I've gone ahead and deleted
> > the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> > (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> > and the Yetus integration.
> >
> > I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> > at a high-level, this means we no longer need to edit CHANGES.txt on new
> > commit, streamlining our commit process. CHANGES.txt updates will still
> be
> > necessary for backports to older release lines like 2.6.x and 2.7.x.
> >
> > Happy committing!
> >
> > Best,
> > Andrew
>
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by Ravi Prakash <ra...@gmail.com>.
Yaayy!! +1
On Tue, Mar 8, 2016 at 10:59 AM, Colin P. McCabe <cm...@apache.org> wrote:
> +1
>
> Thanks, Andrew. This will avoid so many spurious conflicts when
> cherry-picking changes, and so much wasted time on commit.
>
> best,
> Colin
>
> On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com>
> wrote:
> > Hi all,
> >
> > With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> > and release notes are now generated by Yetus. I've gone ahead and deleted
> > the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> > (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> > and the Yetus integration.
> >
> > I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> > at a high-level, this means we no longer need to edit CHANGES.txt on new
> > commit, streamlining our commit process. CHANGES.txt updates will still
> be
> > necessary for backports to older release lines like 2.6.x and 2.7.x.
> >
> > Happy committing!
> >
> > Best,
> > Andrew
>
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by "Colin P. McCabe" <cm...@apache.org>.
+1
Thanks, Andrew. This will avoid so many spurious conflicts when
cherry-picking changes, and so much wasted time on commit.
best,
Colin
On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com> wrote:
> Hi all,
>
> With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> and release notes are now generated by Yetus. I've gone ahead and deleted
> the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> and the Yetus integration.
>
> I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> at a high-level, this means we no longer need to edit CHANGES.txt on new
> commit, streamlining our commit process. CHANGES.txt updates will still be
> necessary for backports to older release lines like 2.6.x and 2.7.x.
>
> Happy committing!
>
> Best,
> Andrew
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by "Colin P. McCabe" <cm...@apache.org>.
+1
Thanks, Andrew. This will avoid so many spurious conflicts when
cherry-picking changes, and so much wasted time on commit.
best,
Colin
On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com> wrote:
> Hi all,
>
> With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> and release notes are now generated by Yetus. I've gone ahead and deleted
> the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> and the Yetus integration.
>
> I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> at a high-level, this means we no longer need to edit CHANGES.txt on new
> commit, streamlining our commit process. CHANGES.txt updates will still be
> necessary for backports to older release lines like 2.6.x and 2.7.x.
>
> Happy committing!
>
> Best,
> Andrew
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by "Colin P. McCabe" <cm...@apache.org>.
+1
Thanks, Andrew. This will avoid so many spurious conflicts when
cherry-picking changes, and so much wasted time on commit.
best,
Colin
On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com> wrote:
> Hi all,
>
> With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> and release notes are now generated by Yetus. I've gone ahead and deleted
> the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> and the Yetus integration.
>
> I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> at a high-level, this means we no longer need to edit CHANGES.txt on new
> commit, streamlining our commit process. CHANGES.txt updates will still be
> necessary for backports to older release lines like 2.6.x and 2.7.x.
>
> Happy committing!
>
> Best,
> Andrew
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Posted by "Colin P. McCabe" <cm...@apache.org>.
+1
Thanks, Andrew. This will avoid so many spurious conflicts when
cherry-picking changes, and so much wasted time on commit.
best,
Colin
On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang <an...@cloudera.com> wrote:
> Hi all,
>
> With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> and release notes are now generated by Yetus. I've gone ahead and deleted
> the manually updated CHANGES.txt from trunk, branch-2, and branch-2.8
> (HADOOP-11792). Many thanks to Allen for the releasedocmaker.py rewrite,
> and the Yetus integration.
>
> I'll go ahead and update the HowToCommit and HowToRelease wiki pages, but
> at a high-level, this means we no longer need to edit CHANGES.txt on new
> commit, streamlining our commit process. CHANGES.txt updates will still be
> necessary for backports to older release lines like 2.6.x and 2.7.x.
>
> Happy committing!
>
> Best,
> Andrew