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 C7460740038 for ; Wed, 31 Jul 2024 14:41:38 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=r1PzNSL4Mykn2F8ph4IWtXrgY9S1wtzKMTBpAqTghcc=; 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=1722436898; v=1; b=wv5SLCrthDnRnRocDNptH/dHRZAqluzrZpqF0yCRFfnXyLnii3xvuq0P2nnCV1Lds5+yCo+k PvOcCWlB9Hj3SllXfRUa3PTzWikSYB4JJqqqjdOs/aTOAsTwGC05jnL7rjactTDfONCRL2QN1Q9 EqTCJOTZqe9UyxMJAwdyXKmnrSJ5NDLU7lxe76uVUdLKO65xy7sqGal5oshLk+tBx++PKTV3wH5 YhzLgZ22eq/Au0bj2s/aO3kYVUA9RJuPI9TonBaHeo1Q6SXLjP8/artuwZyA1qLbGc+GRVrtUiy 9rFY3Yq2tIz/snx7g74XCnDho6Ii0s7AgLuRgwh27M7gQ== X-Received: by 127.0.0.2 with SMTP id aG3qYY7687511xhn6Xrne9RQ; Wed, 31 Jul 2024 07:41:37 -0700 X-Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mx.groups.io with SMTP id smtpd.web10.44410.1722436896714367312 for ; Wed, 31 Jul 2024 07:41:36 -0700 X-Received: from [10.6.0.181] (unknown [20.39.63.14]) by linux.microsoft.com (Postfix) with ESMTPSA id A31F020B7165; Wed, 31 Jul 2024 07:41:35 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com A31F020B7165 Message-ID: <9719c459-ed8a-4251-8888-5c7618979bf6@linux.microsoft.com> Date: Wed, 31 Jul 2024 10:41:34 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub Issues To: devel@edk2.groups.io, michael.d.kinney@intel.com, "rfc@edk2.groups.io" Cc: 'Andrew Fish' , 'Leif Lindholm' , 'Sean Brogan' References: <3edf75ea-1be4-4516-a8b6-efbcc1028596@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 07:41:36 -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: HRvCuqxggWh5gaVqOi8FfWClx7686176AA= 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=wv5SLCrt; 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 >> Proposed Process >> ---------------- >> >> 1. Create GitHub issue templates for the following categories that >> include basic automation of validation for input. >> >> * Bug Report >> >> * Fields: >> * Title >> * Packages Affected >=20 > Would this be free form text or a multi select list of possible packages? Drop down and check boxes are currently supported. To my understanding,=20 multi-select is not. I was planning to instead use check boxes which=20 would still allow multiple selection from a fixed set of options. >> * Current Behavior >> * Expected Behavior >> * Steps to Reproduce >> * Build Environment >> * Host Information (if applicable) such as OS and Tool Chain >> and/or container information >=20 > Would this be free form text or a multi select list of allowed options? For information where we can constrain the options to what is supported=20 in edk2, we can do that (with check boxes), for example, the tool chain=20 list. I planned to make Host OS and container information fields free form. >> >> * Feature Request >> >> * Fields: >> * Title >> * Packages Affected >=20 > Would this be free form text or a multi select list of allowed options? It would be consistent with other forms as check boxes. >> >> * Documentation Request >> >> * Fields: >> * Title >> * Packages Affected >=20 > Would this be free form text or a multi select list of allowed options? >=20 > Some documents are not package specific such as the build system related = documents. > Would the target spec be the right value here? That makes sense. In that case, would you like labels to be defined=20 based on the option selected so requests for individual spec issues can=20 be filtered? >> >> 3. Define GitHub labels that can be manually added: >> >=20 > This set looks good. Please add brief descriptions of that each label re= presents. I will update the live version of this on the GitHub discussion page=20 with descriptions. >> >> 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. >=20 > 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 -=20 https://docs.github.com/issues/using-labels-and-milestones-to-track-work/ab= out-milestones For us, I think of it as equivalent to stable tag release. The milestone=20 terminology is used here because on the issue/PR page that is the GitHub=20 controlled heading under which the appropriate milestone would be selected. >> >> 6. Stage updates to the TianoCore documentation to reflect the new >> process and provide a user guide for transitioning to GitHub Issues >> from Bugzilla. >=20 > Bugzilla supports attachments. How will attachments be migrated to a Git= Hub issue? >=20 > Bugzilla also contains bugs that apply to may different GitHub repos. Wi= ll > all of the Bugzilla issues across all repos be migrated at the same time > 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=20 added. This proposal did not plan to move all bugs at once and mark Bugzilla=20 read-only. I will need to do more extensive research on how feasible=20 that is. Other large open-source projects have successfully made that=20 transition. -=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 (#120152): https://edk2.groups.io/g/devel/message/120152 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-