Re: Experimental opening of php/doc-en issues
[email protected] ("G. P. B.")
| Newsgroups | php.doc |
|---|---|
| Message-ID | <CAFPFaML-hAmdKnHXfgSN8P_seHYEZoTCgufKqjHFiquiq3_9jA@mail.gmail.com> |
On Thu, 21 Oct 2021 at 15:33, Nikita Popov <[email protected]> wrote: > On Tue, May 25, 2021 at 4:31 PM Christoph M. Becker <[email protected]> > wrote: > >> Hi all, >> >> there was some discussion regarding replacing bugsnet with GH issues a >> while ago[1]. Today we decided to open GH issues for doc-en to see how >> this may work out[2]. Nikita provided a PR[3] which changes the "Report >> a bug" link on the manual pages to open an issue on GH instead of a >> ticket on bugsnet. IMHO, this makes sense to make GH issues more >> prominent, so we will be able to more quickly determine whether GH >> issues are actually preferable to bugsnet. >> >> Thoughts? >> >> [1] <https://externals.io/message/114300> >> [2] <https://externals.io/message/114300#114586> >> [3] <https://github.com/php/web-php/pull/407> >> > > To follow up on this, I'd like to disable the option to submit a > "Documentation Problem" on bugs.php.net with > https://github.com/php/web-bugs/pull/107. Instead, submitters are > directed to issues on php/doc-en. This avoids having two places where new > documentation bugs may be submitted. Are there any objections to doing > this? (It's still possible to reclassify submitted bugs as doc problems > after the fact.) > > Regards, > Nikita > Sounds reasonable, I have stopped checking bugs.php.net in regards to doc bugs personally, and having thing in multiple places is a bad idea. George P. Banyard