From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id 498EA780091 for ; Tue, 6 Aug 2024 05:35:01 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=JDYYm/8yu3Bcfgyd0JHHSqwxD4yJX/20hHdjEYwblJU=; c=relaxed/simple; d=groups.io; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Thread-Index:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Transfer-Encoding:Content-Language; s=20240206; t=1722922500; v=1; b=nANeXATfe0gMpQ0ymuKVZUL4g9zFBXgXds/fKoAXfhXfCo98Dy3lvrsDmn8trzRzO6cwWbHI kc1qopR3Wdx89NEzziUHwl+SjtgTf+gb9YyHL6tSy3ARIf6y9GQOeTkL8/6IJN9uJn4RlUITcJ6 287Y+zpS7qTjG3nqv5IbSsM07HwmaRJrPWhijWtwr/5JYRbIbTV8uhR7XZ/5ktRj9CWMgkAimZZ k5q5qZCPsu+Op9XUqp2vvlG75ULmkrnZ+fgdcAH8VMAbpy6KnRHxJFzr9bh+p4mGiciCPiVRf1n ZDTQVMDung315KYQJtcuoe5+VY4xPLzVOgoNYQCm1IzbA== X-Received: by 127.0.0.2 with SMTP id Sm6BYY7687511xXstdAqFCfc; Mon, 05 Aug 2024 22:34:59 -0700 X-Received: from cxsh.intel-email.com (cxsh.intel-email.com [121.46.250.151]) by mx.groups.io with SMTP id smtpd.web11.707.1722922496740105695 for ; Mon, 05 Aug 2024 22:34:58 -0700 X-Received: from cxsh.intel-email.com (localhost [127.0.0.1]) by cxsh.intel-email.com (Postfix) with ESMTP id 6FDE0DDA7EA; Tue, 6 Aug 2024 13:34:51 +0800 (CST) X-Received: from localhost (localhost [127.0.0.1]) by cxsh.intel-email.com (Postfix) with ESMTP id 69686DDA7E9; Tue, 6 Aug 2024 13:34:51 +0800 (CST) X-Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by cxsh.intel-email.com (Postfix) with SMTP id 6F5B8DDA7D1; Tue, 6 Aug 2024 13:34:47 +0800 (CST) X-Received: from DESKTOPS6D0PVI ([58.246.60.130]) (envelope-sender ) by 192.168.6.13 with ESMTP(SSL) for ; Tue, 06 Aug 2024 13:34:16 +0800 X-WM-Sender: gaoliming@byosoft.com.cn X-Originating-IP: 58.246.60.130 X-WM-AuthFlag: YES X-WM-AuthUser: gaoliming@byosoft.com.cn From: "gaoliming via groups.io" To: , , "'Kinney, Michael D'" , Cc: "'Andrew Fish'" , "'Leif Lindholm'" , "'Sean Brogan'" References: <3edf75ea-1be4-4516-a8b6-efbcc1028596@linux.microsoft.com> <9719c459-ed8a-4251-8888-5c7618979bf6@linux.microsoft.com> In-Reply-To: Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0gW1JGQ10gVHJhbnNpdGlvbmluZyBmcm9tIEJ1Z3ppbGxhIHRvIEdpdEh1YiBJc3N1ZXM=?= Date: Tue, 6 Aug 2024 13:34:16 +0800 Message-ID: <01f901dae7c2$483622b0$d8a26810$@byosoft.com.cn> MIME-Version: 1.0 Thread-Index: AQHYkRCQebjaNPjimmP3/8qWgz2pLQHMbacQAVUkXA0CqoA66gMNOwj7sdeSgfA= Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Resent-Date: Mon, 05 Aug 2024 22:34:58 -0700 Resent-From: gaoliming@byosoft.com.cn Reply-To: devel@edk2.groups.io,gaoliming@byosoft.com.cn List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: EzHvYqjsjD3ay1ACXzzHFpIux7686176AA= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: zh-cn X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240206 header.b=nANeXATf; dmarc=pass (policy=none) header.from=groups.io; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io Michael: Thanks for your great effort. This is a good direction to consolidate cod= e and issue together. My feedbacks are below: 1. BugZilla supports code first process. What proposal will handle this pro= cess in Github issue flow? 2. BugZilla supports Edk2-Platform and Edk2-Test repo. After their issues a= re migrated to Github, their code process will be migrated to Github pull r= equest. Right? 3. Edk2 Stable Tag Release Note will list the resolved issue and feature. I= think they can be found in GitHub issue. I will learn the way how to find = them.=20 Thanks Liming > -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6----- > =E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io = =E4=BB=A3=E8=A1=A8 Michael Kubacki > =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2024=E5=B9=B48=E6=9C=881=E6=97=A5 3= :36 > =E6=94=B6=E4=BB=B6=E4=BA=BA: Kinney, Michael D ; > devel@edk2.groups.io; rfc@edk2.groups.io > =E6=8A=84=E9=80=81: 'Andrew Fish' ; 'Leif Lindholm' > ; 'Sean Brogan' > =E4=B8=BB=E9=A2=98: Re: [edk2-devel] [RFC] Transitioning from Bugzilla to= GitHub Issues >=20 > I made updates to the RFC on the GitHub Discussion page with rev tracking= . >=20 > https://github.com/tianocore/edk2/discussions/5926 >=20 > On 7/31/2024 1:56 PM, Kinney, Michael D wrote: > > > > > >> -----Original Message----- > >> From: Michael Kubacki > >> Sent: Wednesday, July 31, 2024 7:42 AM > >> To: devel@edk2.groups.io; Kinney, Michael D ; > >> rfc@edk2.groups.io > >> Cc: 'Andrew Fish' ; 'Leif Lindholm' > >> ; 'Sean Brogan' > >> Subject: Re: [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub > >> Issues > >> >=20 > >>>> > >>>> * Documentation Request > >>>> > >>>> * Fields: > >>>> * Title > >>>> * Packages Affected > >>> > >>> Would this be free form text or a multi select list of allowed option= s? > >>> > >>> Some documents are not package specific such as the build system rela= ted > >> documents. > >>> Would the target spec be the right value here? > >> > >> That makes sense. In that case, would you like labels to be defined > >> based on the option selected so requests for individual spec issues ca= n > >> be filtered? > > > > For the edk2 repo, the documentation requests would have to be limited > > to documents in the edk2 repo itself or perhaps the edk2 Wiki. > > > > Many of build specifications are in independent repos in the tianocore-= docs > > organization. So a GitHub issue opened in one of those spec repos is a= lready > > scoped to the right specification. > > > > So perhaps, the "Packages Affected" field here is same as the code ones > > to request updates to Readme files in the source tree. May need an opt= ion > > to open an issue against the Wiki. >=20 > That aligns more to what I was originally intending within the scope of > the issue in this repo. >=20 > That should mean that this page would be updated to describe a GitHub > issue based process and those spec repos would need a template as well? >=20 > - Today's Spec Documentation: > https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCo= re- > Documents-GitBook-Overview >=20 > - Doc Repos: https://github.com/tianocore-docs >=20 > >>>> > >>>> 4. Define GitHub milestones for the upcoming three edk2 stable tags = so > >>>> that issues can optionally be tracked against those milestones= . > >>>> > >>>> Note: The milestone box is a simple drop down that allows for = easy > >>>> selection of defined milestones. > >>> > >>> Is milestone and release the same thing? Should we just use "release= " > >>> Terminology? Or is there a needs to define one or more milestones > >>> Between releases? > >> > >> "Milestone" is a GitHub name for this concept - > >> https://docs.github.com/issues/using-labels-and-milestones-to-track- > >> work/about-milestones > >> > >> For us, I think of it as equivalent to stable tag release. The milesto= ne > >> terminology is used here because on the issue/PR page that is the GitH= ub > >> controlled heading under which the appropriate milestone would be sele= cted. > > > > Ok. So "Milestone" is the heading, but the values to select from would > > be stable tag names. Right? >=20 > Yes. >=20 > >>>> > >>>> 6. Stage updates to the TianoCore documentation to reflect the new > >>>> process and provide a user guide for transitioning to GitHub I= ssues > >>>> from Bugzilla. > >>> > >>> Bugzilla supports attachments. How will attachments be migrated to a > >> GitHub issue? > >>> > >>> Bugzilla also contains bugs that apply to may different GitHub repos. > >> Will > >>> all of the Bugzilla issues across all repos be migrated at the same t= ime > >>> so Bugzilla can be converted to read-only for all issue types on the = same > >>> date? > >> > >> There will be a box at the bottom of the form where attachments can be > >> added. > >> > >> This proposal did not plan to move all bugs at once and mark Bugzilla > >> read-only. I will need to do more extensive research on how feasible > >> that is. Other large open-source projects have successfully made that > >> transition. > > > > Thanks! Let's start with investigating what needs to be done to do the > > conversion and identify the sequence of tasks and we can discuss next > > steps based on resources available to perform the conversions and set > > feasible dates for the transition. >=20 > Sounds good. >=20 >=20 >=20 >=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#120246): https://edk2.groups.io/g/devel/message/120246 Mute This Topic: https://groups.io/mt/107746608/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-