Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
Yaayy!! +1 On Tue, Mar 8, 2016 at 10:59 AM, Colin P. McCabe 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 > 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
+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 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
Great change! Saving ~1min for each commit. Thanks Andrew and Allen. On Thu, Mar 3, 2016 at 9:32 PM Yongjun Zhang wrote: > That's nice, thanks Andrew and Allen. > > --Yongjun > > On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang > 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 > > > -- Zhe Zhang Apache Hadoop Committer http://zhe-thoughts.github.io/about/ | @oldcap
Re: CHANGES.txt is gone from trunk, branch-2, branch-2.8
That's nice, thanks Andrew and Allen. --Yongjun On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang 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 >
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