Hi Swapnup, I think you are right, there is no benefit to maintaining a separate master branch since we have no way to stage changes before publishing. So I'm +1 on your proposed change.
Thanks, Dave On Sat, Aug 24, 2019 at 12:32 AM Swapnil M Mane <swapnilmm...@apache.org> wrote: > Hello team, > > We have two branches master, and asf-site on Roller website repository [1] > The asf-site branch is deployed at Roller official site [2]. > > This brings us the overhead of maintaining two branches. > Most of the Apache projects [3][4] are maintaining single asf-site branch. > > It seems me, the reason for two branches are > master - default created in Git > asf-site - created for deploying official Roller site [2] > > So, to reduce the overhead of maintaining two branches, > 1. we can make master as Stale (as done for Flink[4]) and > 2. make the asf-site branch as the default branch. > > Please let me know if I am missing any information or history for > maintaining two branches. > > [1] https://github.com/apache/roller-website/ > [2] http://roller.apache.org/ > [3] https://github.com/apache/spark-website/branches > [4] https://github.com/apache/flink-web/branches > > Best regards, > Swapnil M Mane, > www.apache.org >
