Date: Fri, 24 May 2019 10:59:13 +0000 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-ports@freebsd.org Subject: Re: Policy on closing bugs Message-ID: <d075453e-e2e6-9425-45b9-f69a7ebc9770@gjunka.com> In-Reply-To: <20761d93-ec8d-dd79-8472-e06bb6942f51@rlwinm.de> References: <2d6b1503-8ecd-6313-525b-e9f104fcb7f6@gjunka.com> <20761d93-ec8d-dd79-8472-e06bb6942f51@rlwinm.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/05/2019 10:53, Jan Bramkamp wrote: > On 24.05.19 12:07, Grzegorz Junka wrote: >> Hey, >> >> Is there any policy/document when a bug can be closed? For example, >> is it OK to close a bug that is fixed upstream but not yet in ports? >> >> Thanks >> GrzegorzJ >> > I don't know of any official policy, but as a user (and port > maintainer) I would prefer an update to the FreeBSD PR stating that > the bug has been fixed upstream. Closing the PR should wait until the > fix made it into the port. > As a port maintainer and user would you like to see an official guideline/policy about defect states and when to transition between them?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d075453e-e2e6-9425-45b9-f69a7ebc9770>