Dear all, In order to ensure bug fixes are ported to the latest release, I've proposed we do semi-regular "minor" releases of gem5, consisting purely of bug fixes and improvements that don't change functionality or APIs. There's really no fixed schedule for this, but my intention is to make a minor release when we have a nice set of changes we feel should be on the stable branch. This stops the problem of having lots of little "hotfixes" which are not really urgently needed by gem5 users.
I've created a new branch, `minor-release-staging-v21-0-1` : https://gem5-review.googlesource.com/q/project:public%252Fgem5+branch:minor-release-staging-v21-0-1 If you have a patch which you want applied as part of the minor release then you can either: A) Submit directly to this branch (`git push origin HEAD:refs/for/minor-release-staging-v21-0-1`). This branch will be merged into the stable and develop branch upon release. B) Submit to develop, and once merged cherry-pick the change into the minor-release-staging-v21-0-1 branch. I suggest `B)` as this gets a fix on the develop branch faster, and no slower to the stable, but it's up to you. 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 -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
