Hi!
> Status or canned answers?
I'd say both :) Just changing status may be not enough, we need some
kind of text to go with it.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
On Mon, 2016-02-08 at 11:25 -0800, Stanislav Malyshev wrote:
> Hi!
>
> > From a technical perspective anybody who can push to the web-bugs-repo
> > can add a status. The status is just a varchar() field in the database.
> > No admin task needed to change it.
>
> Could you please point out w
Hi!
> From a technical perspective anybody who can push to the web-bugs-repo
> can add a status. The status is just a varchar() field in the database.
> No admin task needed to change it.
Could you please point out where you add the status? I could not find
any places in the code where the canne
On Mon, 2016-02-08 at 14:13 +, Dan Ackroyd wrote:
> On 30 January 2016 at 07:19, Stanislav Malyshev wrote:
> >
> > As far as I can see, the only way to do it is to edit local database, so
> > somebody with shell access and DB password is needed.
>
> What is the process for adding new status t
On 30 January 2016 at 07:19, Stanislav Malyshev wrote:
>
> As far as I can see, the only way to do it is to edit local database, so
> somebody with shell access and DB password is needed.
What is the process for adding new status to those available at
bugs.php.net ? Does anyone know who has acces
Hi!
> It's a good solution to the backlog of issues that have been open for
> years. It also makes it easier to handle new issues as they come up as
> it is more appropriate to put new issues to that state than either
> 'closed' or 'wont fix'.
>
> Who is able to a new 'Requires RFC' state to the
On 16 January 2016 at 00:28, François Laupretre wrote:
> Le 15/01/2016 19:53, Stanislav Malyshev a écrit :
> Not just a standard text, a new specific 'Require RFC' status too, so that
> they can be easily retrieved.
My initial reaction was to not like that ideabut it's grown on me.
It's a go
Le 15/01/2016 19:53, Stanislav Malyshev a écrit :
Hi!
Those that do require RFC I think is fine to close. Maybe have a
standard text for that - like "This request describes a change that is
substantial enough to warrant an RFC. Please read and submit an
RFC for the consideration for the communi
Le 15/01/2016 18:04, Dan Ackroyd a écrit :
If anyone thinks they all ought to be kept open, that could be
discussed on list, but I would really like to avoid discussing each
one individually on list, as I don't think that would be productive.
If anyone with wants to keep any of these issues ope
Hi!
> For old bug reports it might be reasonable to change the status to
> "Feedback" and ask, whether the issue still persists. This way the
> report is likely going to end up with "No feedback", what's IMHO better
> than "Closed" for such cases.
This is a good option too.
--
Stas Malyshev
sm
Stanislav Malyshev wrote:
>> I don't think having them kept open is providing any value, and it
>> makes it harder to find actual issues that need fixing in the issue
>> database, so I'd like to close some of them.
>
> Bug DB triage is a hard, long and often thankless work. I am very
> thankful t
Hi!
> However there are lots of issues open from 'a while ago' that are
> either not really bug requests, or are too old to investigate.
Bug db also has feature requests. Which are fine, even if nobody does
them now, people may do in the future.
> I don't think having them kept open is providing
Hello,
I've been watching the bug database for issues coming in for PHP7, and
there have been far fewer than I was expecting, which is nice.
However there are lots of issues open from 'a while ago' that are
either not really bug requests, or are too old to investigate.
I don't think having them
13 matches
Mail list logo
