Dear all, We are excited to inform you that gem5 is migrating from Gerrit to GitHub for code collaboration and version control. This migration is scheduled to take place on June 15th. We believe that this move will provide a more streamlined and efficient development process for our community. The new gem5 repository will be hosted at the following URL: https://github.com/gem5/gem5. We kindly request all contributors and maintainers to update their references, links, and remote repo settings accordingly. In order to complete this migration, on June 15th the Gerrit Repository will be changed to a read-only state. With this migration, we will be transitioning to a pull-request model for code contributions. This means that contributors will need to undertake following process: 1. Fork the gem5 repository on GitHub. 2. Create a new branch in your forked repository for your feature or bug fix. 3. Commit your changes to the new branch. 4. Push the branch to your forked repository. 5. Open a pull request from your branch in your forked repository to the main gem5 repository. We will continue to use the “develop” branch for development, so please ensure your pull requests are for the gem5 develop branch. Pull requests to the stable branch will be blocked. Each pull request will then be evaluated prior to being merged into develop. The new process for merging code into gem5 requires that: 1. Continuous Integration (CI) tests must pass. These will be run via GitHub Actions when a PR is created or updated. They are equivalent to kokoro tests today. 2. Each pull request must be reviewed and "approved" by at least one reviewer. Like on Gerrit today, anyone can review any changeset. 3. A maintainer must merge the PR, which can only happen after the PR is approved by a reviewer and the CI tests pass. We will give gem5 maintainers these permissions over the next few days. We understand that this transition may require some adjustments, but we believe that it will provide a more collaborative and transparent environment for our community. The GitHub platform offers robust features for code reviews, discussions, and a familiar interface for many developers. The https://github.com/gem5/gem5 repo is, at the time of writing, setup for members of the community to play with and accustom themselves with the process. We encourage developers to create dummy pull-requests and post reviewers. Merging a pull to develop is currently blocked but will be enabled in June 15th when Gerrit is turned read-only. We encourage all community members to actively participate in the migration process and provide feedback or suggestions to make this transition as smooth as possible. As with all big changes we expect teething problems so encourage you to highlight any issues, ask questions, or raise concerns regarding this new model and setup. In addition to the gem5 git repository will be making similar migrations for our gem5-resources and gem5-website repositories. We are also enabling GitHub Issues and GitHub Discussions. Please feel free to use these in place of Jira, gem5-dev, gem5-users, and Slack. Depending on the community's preferences, we may migrate to solely using these GitHub-based tools to simplify the organization of the project. Thank you for your continued support and dedication to the gem5 project. We look forward to this new chapter in our development journey! We will keep close eye on this thread for discussions about this move. We will work over the coming week to update all the website and related documentation to reflect this change and provide the documentation needed to the community. Best regards, Bobby -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net

Dear all, We’re still working on ensuring a smooth migration from Gerrit to Github. We had originally planned to have migration occur yesterday, on the 15th, but found we still need to update documentation and do some further checks to ensure the GitHub testing infrastructure meet our requirements. As such, we wish to re-schedule the transfer to June 27th. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net > On Jun 6, 2023, at 6:50 AM, Bobby Bruce <bbruce@ucdavis.edu> wrote: > > Dear all, > > We are excited to inform you that gem5 is migrating from Gerrit to GitHub for code collaboration and version control. This migration is scheduled to take place on June 15th. We believe that this move will provide a more streamlined and efficient development process for our community. > > The new gem5 repository will be hosted at the following URL: https://github.com/gem5/gem5. We kindly request all contributors and maintainers to update their references, links, and remote repo settings accordingly. In order to complete this migration, on June 15th the Gerrit Repository will be changed to a read-only state. > > With this migration, we will be transitioning to a pull-request model for code contributions. This means that contributors will need to undertake following process: > > 1. Fork the gem5 repository on GitHub. > 2. Create a new branch in your forked repository for your feature or bug fix. > 3. Commit your changes to the new branch. > 4. Push the branch to your forked repository. > 5. Open a pull request from your branch in your forked repository to the main gem5 repository. > > We will continue to use the “develop” branch for development, so please ensure your pull requests are for the gem5 develop branch. Pull requests to the stable branch will be blocked. > > Each pull request will then be evaluated prior to being merged into develop. The new process for merging code into gem5 requires that: > > 1. Continuous Integration (CI) tests must pass. These will be run via GitHub Actions when a PR is created or updated. They are equivalent to kokoro tests today. > 2. Each pull request must be reviewed and "approved" by at least one reviewer. Like on Gerrit today, anyone can review any changeset. > 3. A maintainer must merge the PR, which can only happen after the PR is approved by a reviewer and the CI tests pass. We will give gem5 maintainers these permissions over the next few days. > > We understand that this transition may require some adjustments, but we believe that it will provide a more collaborative and transparent environment for our community. The GitHub platform offers robust features for code reviews, discussions, and a familiar interface for many developers. The https://github.com/gem5/gem5 repo is, at the time of writing, setup for members of the community to play with and accustom themselves with the process. We encourage developers to create dummy pull-requests and post reviewers. Merging a pull to develop is currently blocked but will be enabled in June 15th when Gerrit is turned read-only. > > We encourage all community members to actively participate in the migration process and provide feedback or suggestions to make this transition as smooth as possible. As with all big changes we expect teething problems so encourage you to highlight any issues, ask questions, or raise concerns regarding this new model and setup. > > In addition to the gem5 git repository will be making similar migrations for our gem5-resources and gem5-website repositories. We are also enabling GitHub Issues and GitHub Discussions. Please feel free to use these in place of Jira, gem5-dev, gem5-users, and Slack. Depending on the community's preferences, we may migrate to solely using these GitHub-based tools to simplify the organization of the project. > > Thank you for your continued support and dedication to the gem5 project. We look forward to this new chapter in our development journey! We will keep close eye on this thread for discussions about this move. We will work over the coming week to update all the website and related documentation to reflect this change and provide the documentation needed to the community. > > Best regards, > Bobby > > -- > Dr. Bobby R. Bruce > Room 3050, > Kemper Hall, UC Davis > Davis, > CA, 95616 > > web: https://www.bobbybruce.net >