Hi Giacomo, This is a great suggestion! Thanks for making this more clear.
We'll update our contributing guide (coming soon!) with this information. Cheers, Jason On Mon, Dec 2, 2019 at 5:45 AM Giacomo Travaglini <[email protected]> wrote: > > Hi devs, > > I am very happy that we finally have a bug/feature tracker (thanks to Bobby > and Jason): > > https://gem5.atlassian.net/projects/GEM5/issues > > This is very powerful IMHO when it comes to pushing a big chunk of patches. > Usually most of them are refactoring patches preparing for the actual feature > implementation > or bug fix. > > Sometimes, when I start reviewing them, it takes quite some time to > understand the context or > the purpose of them, unless a description of what they are trying to achieve > is provided through this > mailing list. > > I strongly suggest to use JIRA on that purpose: creating a ticket describing > the issue and > possibly linking the first patch (or maybe all?) of the patchset to the > ticket itself (in the commit message). > This will likely reduce the review time, since a reviewer will have an idea > of what the owner > is trying to achieve. > > Pardon me if this reminder seems obvious and unnecessary, > > Giacomo > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
