> -----Original Message----- > From: Laszlo Ersek [mailto:ler...@redhat.com] > Sent: Thursday, July 21, 2016 6:15 AM > To: Kinney, Michael D <michael.d.kin...@intel.com> > Cc: edk2-devel-01 <edk2-de...@ml01.01.org> > Subject: Re: [edk2] Tianocore Bugzilla Server is now live > > On 07/21/16 00:47, Kinney, Michael D wrote: > > Hello, > > > > I am pleased to announce that the Bugzilla server for Tianocore > > is now live and ready to be used. The server URL is: > > > > https://tianocore.acgmultimedia.com > > > > If you do not have a user account yet, please create one. > > > > There is also a new mailing list called edk2-b...@lists.01.org. > > Bugzilla has been configured so all new issues and all state > > changes to issues are sent to this mailing list. If you want > > to see every state change on every issue, then you can sign > > up to this mailing list at: > > > > https://lists.01.org/mailman/listinfo/edk2-bugs > > > > There is one special Product type on the Bugzilla server called > > "Tianocore Security Issues". If you believe you have discovered > > a security issue, then you must enter the issue using the > > "Tianocore Security Issues" Product. The issue will be evaluated > > to determine if it really is a security issue or not. > > > > NOTE: Never any security issue details in email. > > > > I am also updating the Tianocore web pages with the information > > from this email along with additional details in how different > > types of issues are processed. > > > > I will transfer issues from GitHub issue tracker to Bugzilla over > > the next day or two and the GitHub issue tracker for Tianocore > > repositories will be disabled. > > Thanks a lot for this! > > Would it be possible to cross-reference the new BZs with the (soon to > be) old GitHub issues? Something like, > > - for each open GitHub issue, > - open a new BZ > - migrate the data > - add a comment or metadata reference to the BZ that points to the > github issue, > - add a comment to the github issue that: > - references the BZ > - asks the GitHub issue participants to subscribe to the BZ > - close the github issue > - make the github issue tracker read-only > > I'm unsure what "disabling the GitHub issue tracker" means -- will it > become invisible, or just read-only? I think read-only would be > superior; we have a number of commit messages that reference GitHub > issues by URL.
Unfortunately, it does not appear that GitHub supports a read-only setting. The issue tracker is either on or off. I tried an experiment with my personal github area to create an issue in one of my repositories and then turn off issue tracking and see if I can still access the web link to the a single issue and that does not work. I have already created a new BZ issues for every open issue in edk2 GitHub and have transferred all the information into the BZ issue. > > Thanks! > Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
