Hi Michael, We have edk2-devel mailing list today for patch submissions/review and design/implementation discussions.
The commit messages in the future should include a link to the Bugzilla issue(s) the patch addresses. If there are lively discussion on edk2-devel on root causing a bug or discussions on where and how the bug should be fixed in code, then the Bugzilla entry can include gmane links to those edk2-devel threads. I expect we will refine the commit message requirements and Bugzilla issue entry requirements as we use it. Mike From: Michael Zimmermann [mailto:sigmaepsilo...@gmail.com] Sent: Tuesday, July 19, 2016 10:59 AM To: Kinney, Michael D <michael.d.kin...@intel.com> Cc: Laszlo Ersek <ler...@redhat.com>; edk2-devel@lists.01.org <edk2-de...@ml01.01.org> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events how will this work side-by-side with the mailing list? It kinda sounds like a mailing list replacement, and you probably don't want to have separate mailing list topics and bugzilla reports about the same thing. Thanks Michael On Tue, Jul 19, 2016 at 7:24 PM, Kinney, Michael D <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>> wrote: Laszlo, Thanks for the feedback. A few responses embedded below. I agree there are many ways to organize this content inside Bugzilla and that we can refine the products/components/fields as we use it. Mike > -----Original Message----- > From: Laszlo Ersek [mailto:ler...@redhat.com<mailto:ler...@redhat.com>] > Sent: Wednesday, July 6, 2016 12:53 PM > To: Kinney, Michael D > <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>> > Cc: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org> > <edk2-de...@ml01.01.org<mailto:edk2-de...@ml01.01.org>> > Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events > > On 07/06/16 20:52, Kinney, Michael D wrote: > > Laszlo, > > > > Good timing. I was going to send a status update today. > > > > We are working diligently to get Bugzilla online for all bugs. There > > are a few logistics that are still being worked this week related to > > an email list for bug state changes that Jordan is helping with and > > setting up tianocore domain name for the Bugzilla server. > > > > I see many developers have created accounts on the Bugzilla server > > that is in a test mode right now. Thank you to everyone who has done > > that already! If you have not done so, please go to the following > > link and create an account. > > > > https://tianocore.acgmultimedia.com > > > > Also, please enter some sample bugs and feature requests and review > > the fields. Please send feedback if you would like to see any changes > > to the fields. > > > > I will send updates as tasks are completed as I also want to see us > > move to Bugzilla ASAP. This is my highest priority task right now. > > I skimmed the "new bug page" (with the advanced fields shown) for > TestProduct -- from a cursory look, it's fine. > > Other than that, why is "Feature Requests" a separate product from "EDK2 > - Main Trunk"? Same for "UEFI Security Issues". I think feature requests > and security issues should not be separate products. They should be > orthogonal to any product. In the RH Bugzilla at least, these "traits" > are represented by Keywords. Security issues are in a separate product so we can associate then with the "infosec" group for evaluation in the UNCONFIRMED state and support the filtering of email contents if a security issue is embargoed for a period of time. I am working on the detailed process that will be used for these types of issues and will update tianocore web pages with the details for both normal bugs and security issues. I am working through a few details today to reduce the number of products. * "Test Product" will be removed. This was just to evaluate before going live. * I have renamed to "Tianocore Feature Requests". This is to cover feature requests not only for EDK II code/tools/docs, but also for things like the web site, wiki pages, dev process, testing process, release process, etc. * I am going to remove "UDK" and update "EDK2" to add a field to identify both where the issue was observed (EDK2 trunk, UDK 2015, UDK 2014, etc). and where the issue need to be fixed (EDK2 trunk, UDK 2015, UDK 2014, etc). > > Regarding the "EDK2 - Main Trunk" product, I see three components, Code, > Documentation, and Test. I think "component" should correspond to any > entity in the edk2 tree that has a well defined set of maintainers -- > currently, top level Pkg directories. When a feature or bugfix affects > several components, then the original bug is cloned for the other > component(s) -- see the "Clone This Bug" link -- and then the bug > dependencies are adjusted as necessary. > > (In the GitHub issue tracker, we have "labels" for the top Pkg > directories, plus a few orthogonal labels (e.g. Feature, Udk-xxxx, > UdkOnly).) > > Hm... I'm just noticing the custom Package box. When I hover over it, it > says "A custom Multiple-Selection Box field in this installation of > Bugzilla". I think I understand the idea, but it might mix well with > searching. The Advanced Search page allows filtering for Package only in > the Custom Search section, which I find a bit unwieldy. > > Also, the multi-selection is not flexible enough to express dependencies > between packages (BZ cloning is). Not sure I understand what you mean here. Can you provide an example? > > On the positive side, the Package box is available on the Enter Bug page > as well, after showing the Advanced Fields. > > ... Just trying to apply my experience with the RH bugzilla; it may not > be a perfect fit, of course. If we end up with something different here, > I'll be happy to learn it. :) I'm not suggesting that the above remarks > be addressed ASAP, "or else". :) I think the fields can be tweaked (the > database can be converted) later on as well; I wouldn't like to cause > any delays. > > Thanks! > Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org> https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
