Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74754
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH4=i0j1eP_vTkpV+9V=G6nr=jAaNzqDrTs+mm6V--D1PQ@mail.gmail.com>
References: <CAH-PCH4=i0j1eP_vTkpV+9V=G6nr=jAaNzqDrTs+mm6V--D1PQ@mail.gmail.com>
Date: Thu, 5 Jun 2014 20:24:30 +0800
Message-ID: <CAHMUw2Ed+nT==pDQ0A4HmbOq7HHrZZ_e=01efOZAZ1gwfsR0ug@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd6c318a6414c04fb15d330
Subject: Re: [PHP-DEV] should every bugfix have a bugreport?
From: tjerk.meesters@gmail.com (Tjerk Meesters)

--047d7bd6c318a6414c04fb15d330
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 5, 2014 at 8:00 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

> Hi,
>
> I think it would be really nice, if we could have a policy that bugfixes
> should always have an issue on http://bugs.php.net.
> Of course if the bug was spotted and fixed before a public (stable or qa)
> release was made should be excluded from this rule.
> So when fixing the bug and adding the NEWS entry for a bug which wasn't
> reported through the bugtracker, then one should check the bug database a=
nd
> if no report is found he/she should create one.
> For the projects/exts which are using other type of bugtracker (opcache a=
nd
> phpdbg comes to mind with the github issues), those would be ok to use.
>
> Having this policy would mean a bit more work for those fixes which doesn=
't
> have an issue at hand, but I think it would still worth it for the
> following reasons:
>
>    - sometimes explaining the need for the change or why do we have to fi=
x
>    that way can't be summarized in a commit comment.
>    - the NEWS entry is also used for the changelog (
>    http://php.net/ChangeLog-5.php) and for the release announcements, and
>    if somebody want's to complain about some change that we made, it is
> easier
>    to reference it if there is a bug linked to it.
>
> what do you think?
>

+1. I use the bug numbers to author test cases (bug + nr . phpt), so it's
already part of my own workflow :)


> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>



--=20
--
Tjerk

--047d7bd6c318a6414c04fb15d330--