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 224DDAC1A46 for ; Wed, 31 Jul 2024 19:36:38 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=/nQxrtIA6NjgVWUm5TGhVAuIf/U4UqSO0inHK5RkCh4=; c=relaxed/simple; d=groups.io; h=DKIM-Filter:Message-ID:Date:MIME-Version:User-Agent:Subject:To:Cc:References:From:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Language:Content-Type:Content-Transfer-Encoding; s=20240206; t=1722454598; v=1; b=Mgu3oQqDKuOa4XEP0adaotEXzOduDyVEw6edt8bRFmlEIbWPzp9wgwl9Li7s39Z/ZGB/1sb+ ARbnrtdX3F/ExhBsoiSNz5BUKVcWLRy5l8pMuJ4jWjko1P1VGd3hfSlNt8YN0Eo4VDrd2r1oY20 zfOic/48b1nDVvGJ5i/rirp5/xFLZqC5xT0li412LSfdgufN610jeJQRZz7KfYSfUlmnP8Tgf4k sKY+94cwcRXnCv0N3pLAPCtBierpkRXG7ChmdyXpzi6+xvZ4vEYnYoRCLUCNnQGvhrWRuFvQ7W6 pUij8ZpXN0kTGvuyqTtW31xVBqCjA/SBGkaTK5th0DGjw== X-Received: by 127.0.0.2 with SMTP id ALfaYY7687511xZkglIObXUF; Wed, 31 Jul 2024 12:36:37 -0700 X-Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mx.groups.io with SMTP id smtpd.web11.51710.1722454591868624275 for ; Wed, 31 Jul 2024 12:36:31 -0700 X-Received: from [10.6.0.181] (unknown [20.39.63.5]) by linux.microsoft.com (Postfix) with ESMTPSA id 92FEC20B7165; Wed, 31 Jul 2024 12:36:30 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 92FEC20B7165 Message-ID: Date: Wed, 31 Jul 2024 15:36:29 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub Issues To: "Kinney, Michael D" , "devel@edk2.groups.io" , "rfc@edk2.groups.io" Cc: 'Andrew Fish' , 'Leif Lindholm' , 'Sean Brogan' References: <3edf75ea-1be4-4516-a8b6-efbcc1028596@linux.microsoft.com> <9719c459-ed8a-4251-8888-5c7618979bf6@linux.microsoft.com> From: "Michael Kubacki" In-Reply-To: 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: Wed, 31 Jul 2024 12:36:32 -0700 Resent-From: mikuback@linux.microsoft.com Reply-To: devel@edk2.groups.io,mikuback@linux.microsoft.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: aEKSd2HawtK9bzAcz05pIzgXx7686176AA= Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240206 header.b=Mgu3oQqD; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=linux.microsoft.com (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io I made updates to the RFC on the GitHub Discussion page with rev tracking. https://github.com/tianocore/edk2/discussions/5926 On 7/31/2024 1:56 PM, Kinney, Michael D wrote: >=20 >=20 >> -----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 >> >>>> >>>> * Documentation Request >>>> >>>> * Fields: >>>> * Title >>>> * Packages Affected >>> >>> Would this be free form text or a multi select list of allowed options? >>> >>> Some documents are not package specific such as the build system relate= d >> 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 can >> be filtered? >=20 > For the edk2 repo, the documentation requests would have to be limited > to documents in the edk2 repo itself or perhaps the edk2 Wiki. >=20 > Many of build specifications are in independent repos in the tianocore-do= cs > organization. So a GitHub issue opened in one of those spec repos is alr= eady > scoped to the right specification. >=20 > 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 optio= n > to open an issue against the Wiki. That aligns more to what I was originally intending within the scope of=20 the issue in this repo. That should mean that this page would be updated to describe a GitHub=20 issue based process and those spec repos would need a template as well? - Today's Spec Documentation:=20 https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore= -Documents-GitBook-Overview - Doc Repos: https://github.com/tianocore-docs >>>> >>>> 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 ea= sy >>>> 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 milestone >> terminology is used here because on the issue/PR page that is the GitHub >> controlled heading under which the appropriate milestone would be select= ed. >=20 > Ok. So "Milestone" is the heading, but the values to select from would > be stable tag names. Right? Yes. >>>> >>>> 6. Stage updates to the TianoCore documentation to reflect the new >>>> process and provide a user guide for transitioning to GitHub Iss= ues >>>> 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 tim= e >>> so Bugzilla can be converted to read-only for all issue types on the sa= me >>> 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. >=20 > 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. Sounds good. -=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 (#120158): https://edk2.groups.io/g/devel/message/120158 Mute This Topic: https://groups.io/mt/107442879/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-