Re: should every bugfix have a bugreport?

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 and > if no report is found he/she should create one. > For the projects/exts which are using other type of bugtracker (opcache and > 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 fix > 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ács > @Tyr43l - http://tyrael.hu > -- -- Tjerk