[Bug 264484] Problem report lifecycle terminology doesn't match current practice.
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264484] Problem report lifecycle terminology doesn't match current practice."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264484] Problem report guidelines page is out dated and doesn't match current practice"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264484] Problem report guidelines page is out dated and doesn't match current practice"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 05 Jun 2022 17:08:30 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264484
Bug ID: 264484
Summary: Problem report lifecycle terminology doesn't match
current practice.
Product: Documentation
Version: Latest
Hardware: Any
URL: https://docs.freebsd.org/en/articles/pr-guidelines/#pr
-lifecycle
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Books & Articles
Assignee: doc@FreeBSD.org
Reporter: pauamma@gundo.com
CC: bugmeister@FreeBSD.org
Flags: maintainer-feedback?(bugmeister@FreeBSD.org)
CC: bugmeister@FreeBSD.org
I think that:
- what it calls "needs triage" is currently called "new"
- what it calls "in discussion" is currently called "in progress"
- what it calls "patch ready" and "needs MFC") no longer exist or aren't used
currently (although see the patch-ready for the former)
- what it calls "issue resolved" is currently "closed" with resolution "fixed"
but I can't swear to it.
While there, maybe review the rest of it for currency.
Spotted while rooting around for when/why to MFC info.
--
You are receiving this mail because:
You are the assignee for the bug.