+1

Thanks for getting the ball rolling on this, Bobby!

On Fri, Aug 28, 2020 at 5:26 PM Bobby Bruce via gem5-dev <gem5-dev@gem5.org>
wrote:

> Dear all,
>
> Back when we moved from the master branch being under constant development
> to a dual "master-as-stable" and "develop" branch setup, there was talk of
> renaming the master branch. Though, at this time, it seemed unconventional
> so avoided doing so. In the past few months there has been greater momentum
> in the direction of allowing git repositories to call their default branch
> whatever they wish. For example, Github is reworking things in this regard (
> https://github.com/github/renaming/) and defaulting new repos to have
> "main" as the default branch.
>
> Our GoogleSource/Gerrit setup allows us to set HEAD to point towards
> whatever branch we wish. We therefore think v20.1 would be a good time to
> rename "master" to "stable". This afternoon I created a "stable" branch,
> identical to "master", here:
> https://gem5.googlesource.com/public/gem5/+/refs/heads/stable. The next
> step would be to redirect HEAD to this branch, then delete the master
> branch. Coinciding this with the release of v20.1 (in roughly 2 weeks time)
> seems like an ideal timing.
>
> I'm writing this email to ask if the community agrees with this, and if
> there is anything I'm not taking into account. I believe this should be a
> fairly seamless transition, and will give our two branches more descriptive
> names  --- stable and develop.
>
> Kind regards,
> Bobby
> --
> Dr. Bobby R. Bruce
> Room 2235,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
> web: https://www.bobbybruce.net
> _______________________________________________
> gem5-dev mailing list -- gem5-dev@gem5.org
> To unsubscribe send an email to gem5-dev-le...@gem5.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to