<div dir="ltr">I'm very supportive of this switch, but I do think that the timing leaves a bit to be desired. Many people will be taking time off for the holidays at the end of the year, and forcing a change to be complete by week 1 of the new year (since January 7 is part of our first work-week in 2021), might make things more difficult than they should be. This is also problematic because lots of organizations might be subject to production freezes during this time, so they won't be able to do as much testing as they would want before having to switch over. Could we perhaps push back the end date by 2-4 weeks to ensure that nobody has to work through the holidays and/or have an extra stressful first work-week of 2021?<div><br></div><div>Thanks,</div><div>Steve</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 13, 2020 at 5:10 PM Mehdi AMINI via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 13, 2020 at 4:53 PM James Y Knight via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto">I notice that on <a href="https://github.com/github/renaming" rel="noreferrer" target="_blank">https://github.com/github/renaming</a> it says:</div><strong><div dir="auto"><strong><br></strong></div></strong>"""If you haven’t renamed your default branch yet, consider waiting until <a href="https://github.com/github/renaming#later-this-year" rel="noreferrer noreferrer" target="_blank">later this year</a>.
We’re investing in tools to make renaming the default branch of an
existing repository a seamless experience for both maintainers and
contributors."""<div dir="auto"><br></div><div dir="auto">Is that not relevant/not useful for us to wait for that?</div></div></blockquote><div><br></div><div>They expand on this at the end of the document: <a href="https://github.com/github/renaming#later-this-year-seamless-move-for-existing-repositories-" target="_blank">https://github.com/github/renaming#later-this-year-seamless-move-for-existing-repositories-</a></div><div>None of the items seemed particularly helpful. The main feature I'd have wanted would have a server side mirroring of main to master, but we can emulate this with a github action (as Mike plans to do).</div><div><br></div><div>-- </div><div>Mehdi</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, Nov 13, 2020, 6:57 PM Mike Edwards via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer noreferrer" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Everyone,<br><div>Many tech communities, including <a href="https://github.com/github/renaming" rel="noreferrer noreferrer noreferrer" target="_blank">GitHub</a> and <a href="https://sfconservancy.org/news/2020/jun/23/gitbranchname/" rel="noreferrer noreferrer noreferrer" target="_blank">Git</a>,
have moved away from term “master branch” and replaced it with “main
branch” in an</div><div> effort to remove unnecessary references to slavery and use
more inclusive terms. This was also discussed on the <a href="https://lists.llvm.org/pipermail/llvm-dev/2020-June/142445.html" rel="noreferrer noreferrer noreferrer" target="_blank">LLVM-dev mailing list</a><br></div><div>and
there was strong consensus from LLVM Developers’ that the LLVM Project
should also rename our master branch as well. Now that</div><div> an industry
standard name has been selected by GitHub, the LLVM Project can begin
the renaming process of the default branch to “main”. </div><font color="#888888"></font><br><b>This change will occur at **06:00GMT on Monday December 7, 2020** (time is **GMT**, please adjust for your local timezone).</b><br><br>To make this as easy as possible we plan to do the following <b>prior to November 20, 2020</b>:<br>* Create a new branch named 'test-main' on the llvm-project repository<br> * This branch will be read-only except for the llvmbot account<br> * Setup a GitHub action to mirror commits from 'master' to ‘test-main' automatically<br> * Allow the configuration to soak for a few days to ensure everything works<br>* Create a new branch named “main” on the llvm-project repository<br> * This branch will be readonly initially<br> * Reuse the previous Github Action to mirror master to main<br> * This configuration will stay in place until cutover takes place on Dec. 7 <br><br><b>On December 7, 2020</b>:<br>* We will lock the master branch and change it to be readonly (with the exception of llvmbot)<br>* Switch the GitHub action to mirror commits from the new main branch back to the old master branch<br>* Make a few test commits to ensure the GitHub action is functioning as expected<br>* Open the main branch to commits from community members<br>* In parallel we will begin to work through the rest of the llvm organization repositories to update branch names as well<br>* We will update the developer policy to reflect the change in workflow<br><br><b>On January 7, 2021</b>:<br>* We will remove the ‘master’ branch from all repositories in the llvm organization<br><br>As we work towards December 7, 2020 we are going to set up a test of this system on a fork of the llvm-project<br>in order to simulate the cutover. If we encounter any issues we will update the community on llvm-dev.<br>We expect the llvm-project repository to be unavailable to developers for approximately 1 hour while the<br>switch is made. Lockout will occur promptly at 06:00GMT on the 7th. Certainly if we finish sooner, we will<br>update llvm-dev to let everyone know the repository is available for use once again.<br><br>We know this has been a long process and we want to thank everyone for their patience. We look forward to getting<br>the project completed soon.<br><br>Respectfully,<br><br>Mike Edwards<br>On Behalf Of the LLVM Foundation<br></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer noreferrer noreferrer" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div></div></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>