Hi folks. I've uploaded many reviews recently, and there is another large batch on the way. I really appreciate how there has been good engagement on some of the reviews since I know everyone is busy, and few have a vested interest in my projects.
To try to keep the reviews from piling up and never getting in, or getting in with insufficient review, some of my colleagues (Yu-hsin and Jui-min) from Google are going to help out. This will be a great opportunity for them to get more involved with upstream and learn more about the guts of gem5, and for us to be able to contribute more and more efficiently to upstream. This is of course not intended in *any way* to decrease the value of other people's reviews, or diminish the importance of their feedback. If you want to review a change or if you have concerns about something, please don't hesitate to jump in and participate, this is just to help unload the current choke point, which are the busy schedules of other volunteers. One thing in particular that this may not help with are places where there are requests for some sort of additional testing, for instance to make sure we don't break our fairly new RISCV support which is being actively worked on. I think the best way to address this is to have some sort of testing criteria, either manual or automatic, so that changes aren't blocked forever waiting for testing nobody either can or has time to do. If you can at least *describe* what testing should be done, then that will enable someone else to either perform the testing themselves, or even ideally automate the testing and put it into our framework. Anyway, I just wanted to let everyone know what's going on and what to expect. Thanks! Gabe
_______________________________________________ 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
