On Thu, 21 Oct 2021, 22:46 Nikita Popov, wrote:
> On Thu, Oct 21, 2021 at 10:42 PM Jakub Zelenka wrote:
>
>> On Thu, Oct 21, 2021 at 4:07 PM Nikita Popov
>> wrote:
>>
>>>
>>> I'm proposing the following label structure (the list at
>>> https://github.com/nikic/test-repo/labels is incomplete tho
On Thu, Oct 21, 2021 at 10:42 PM Jakub Zelenka wrote:
> On Thu, Oct 21, 2021 at 4:07 PM Nikita Popov wrote:
>
>>
>> I'm proposing the following label structure (the list at
>> https://github.com/nikic/test-repo/labels is incomplete though): Each
>> report has either a bug or feature label. Addit
On Thu, Oct 21, 2021 at 4:07 PM Nikita Popov wrote:
>
> I'm proposing the following label structure (the list at
> https://github.com/nikic/test-repo/labels is incomplete though): Each
> report has either a bug or feature label. Additionally it starts out with
> the T-needs-triage label. Once a p
On Sun, May 9, 2021 at 8:49 AM Joe Watkins wrote:
> Morning internals,
>
> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> waste time deleting 20 odd messages from bugsnet yesterday and this is a
> common, daily occurrence. We clearly don't have time for this.
>
> Quite
On 10.05.2021 at 15:39, Andreas Heigl wrote:
> Hey All
>
> Am 10.05.21 um 14:44 schrieb Alexander Kurilo via internals:
>> On 09/05/2021 09:48, Joe Watkins wrote:
>>> Morning internals,
>>>
>>> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
>>> waste time deleting 20 odd m
Le 09/05/2021 à 08:48, Joe Watkins a écrit :
Having moved our workflow to github, now seems to be the time to seriously
consider retiring bugsnet for general use, and using the tools that are
waiting for us - Github Issues.
Please NO
This mean we will drop ownership on all data and history ab
Hey All
Am 10.05.21 um 14:44 schrieb Alexander Kurilo via internals:
> On 09/05/2021 09:48, Joe Watkins wrote:
>> Morning internals,
>>
>> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
>> waste time deleting 20 odd messages from bugsnet yesterday and this is a
>> common,
On 09/05/2021 09:48, Joe Watkins wrote:
Morning internals,
We have a spam problem on bugsnet, it's not a new problem. Nikita had to
waste time deleting 20 odd messages from bugsnet yesterday and this is a
common, daily occurrence. We clearly don't have time for this.
Quite aside from spam probl
On Sun, May 9, 2021 at 8:49 AM Joe Watkins wrote:
> Morning internals,
>
> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> waste time deleting 20 odd messages from bugsnet yesterday and this is a
> common, daily occurrence. We clearly don't have time for this.
>
> Quite
> On May 9, 2021, at 4:58 AM, Rowan Tommins wrote:
>
> On 9 May 2021 08:33:08 BST, Stanislav Malyshev wrote:
>> It is not good that our infrastructure is "hidden away in a dark
>> corner", and it is true that bugs needs some TLC for a while. But
>> Github
>> Issues frankly sucks big time as a
On Sun, May 9, 2021 at 8:26 AM Larry Garfield wrote:
>
> On Sun, May 9, 2021, at 1:48 AM, Joe Watkins wrote:
> > Morning internals,
> >
> > We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> > waste time deleting 20 odd messages from bugsnet yesterday and this is a
> > comm
On 9/05/2021 8:48, Joe Watkins wrote:
I'm aware that bugsnet serves as the disclosure method for security bugs
and github doesn't have a solution to that. Leaving that to one side for
now ...
Just want to weigh in on this item (also mentioned by Stanislav as an
important issue). Although Github
Hi,
> Having moved our workflow to github, now seems to be the time to seriously
> consider retiring bugsnet for general use, and using the tools that are
> waiting for us - Github Issues.
>
+1, I have been dealing with bugsnet quite a bit as part of maintaining
openssl ext and FPM and it really
On Sun, May 9, 2021, at 1:48 AM, Joe Watkins wrote:
> Morning internals,
>
> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> waste time deleting 20 odd messages from bugsnet yesterday and this is a
> common, daily occurrence. We clearly don't have time for this.
>
> Qui
You're talking about bugs.php.net, right? If you decide to move it, please
leave the old one online in readonly mode. It's a valuable documentation
resource.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Den søn. 9. maj 2021 kl. 09.49 skrev Joe Watkins :
>
> Morning internals,
>
> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> waste time deleting 20 odd messages from bugsnet yesterday and this is a
> common, daily occurrence. We clearly don't have time for this.
Big +1
Am 09.05.2021 um 08:48 schrieb Joe Watkins:
Having moved our workflow to github, now seems to be the time to seriously
consider retiring bugsnet for general use, and using the tools that are
waiting for us - Github Issues.
Yes, please. Thank you for proposing this!
I propose that we disable b
Morning internals,
We have a spam problem on bugsnet, it's not a new problem. Nikita had to
waste time deleting 20 odd messages from bugsnet yesterday and this is a
common, daily occurrence. We clearly don't have time for this.
Quite aside from spam problems, bugsnet is hidden away in a dark corn
On 18.07.2019 at 16:25, Sara Golemon wrote:
> On Thu, Jul 18, 2019 at 6:10 AM Christoph M. Becker
> wrote:
>
>> I agree that this would be the best solution in the long run, and it
>> shouldn't be hard to adapt ReasonRepository[1] to read from a file
>> instead of the DB.
>>
>> Any volunteers?
>>
On Thu, Jul 18, 2019 at 6:10 AM Christoph M. Becker
wrote:
> I agree that this would be the best solution in the long run, and it
> shouldn't be hard to adapt ReasonRepository[1] to read from a file
> instead of the DB.
>
> Any volunteers?
>
> [1]
> <
> http://git.php.net/?p=web/bugs.git;a=blob;f
On Thu, 2019-07-18 at 12:24 +0100, Peter Cowburn wrote:
> I'm not sure if anyone other than us is still using this source code
> (looking at the MySQL guys). If not, can we just include the reasons
> in
> the source directly, and forget about the database or a special file
> containing the reasons
Hey all,
I think we can just add the reasons to the file where it is being rendered.
I am off for the weekend, but I can implement and test this after the weekend
if nobody else picked it up by then.
Pieter
- Original Message -
> From: "Peter Cowburn"
> On Thu, 18 Jul 2019 at 12:10, Ch
On Thu, 18 Jul 2019 at 12:10, Christoph M. Becker wrote:
> On 18.07.2019 at 01:14, Stanislav Malyshev wrote:
>
> >> the quick fix descriptions of bugs.php.net[1] need some update. To my
> >> knowledge, these come from the database, so could anybody with access to
> >> it please take a look?
> >
On 18.07.2019 at 01:14, Stanislav Malyshev wrote:
>> the quick fix descriptions of bugs.php.net[1] need some update. To my
>> knowledge, these come from the database, so could anybody with access to
>> it please take a look?
>
> Ideally, I think this should be in PHP file and not database, so it
Hi!
> the quick fix descriptions of bugs.php.net[1] need some update. To my
> knowledge, these come from the database, so could anybody with access to
> it please take a look?
Ideally, I think this should be in PHP file and not database, so it will
be modifyable by project members without needin
On Wed, Jul 17, 2019 at 4:19 AM Christoph M. Becker
wrote:
> the quick fix descriptions of bugs.php.net[1] need some update. To my
> knowledge, these come from the database, so could anybody with access to
> it please take a look?
>
>
Yep. bugdb_resolves table.
How about though, instead of requi
Hi all,
the quick fix descriptions of bugs.php.net[1] need some update. To my
knowledge, these come from the database, so could anybody with access to
it please take a look?
Details:
* Try a snapshot
There are no snapshots (except for Windows) any longer; it might make
sense to refer to Git.
Morning Ferenc,
That was a good read, and echos my thoughts in places.
I never intended to do anything without explanation, that would obviously
have to be provided.
What I was hoping to extract from this conversation is some criteria for
the updating of bugs: What we actually consider old, what
On Sun, Jan 8, 2017 at 7:46 AM, Joe Watkins wrote:
> Morning internals,
>
> Some of you may have noticed that a few of us have put considerable effort
> into cleanup of pull requests on github, these are now manageable and I'm
> quite confident that we will be able to merge pull requests in a tim
W dniu 17.01.2017 o 18:47, Niklas Keller pisze:
2017-01-17 18:22 GMT+01:00 Andreas Heigl :
Hi All.
Am 17.01.17 um 17:51 schrieb Christoph M. Becker:
On 17.01.2017 at 17:35, Stanislav Malyshev wrote:
People can now cross-reference issues, discuss, get notifications, and
have some simplified/
2017-01-17 18:22 GMT+01:00 Andreas Heigl :
> Hi All.
>
> Am 17.01.17 um 17:51 schrieb Christoph M. Becker:
> > On 17.01.2017 at 17:35, Stanislav Malyshev wrote:
> >
> >>> People can now cross-reference issues, discuss, get notifications, and
> >>> have some simplified/readable markup.
> >>
> >> Al
On 1/17/17 10:39 AM, Marco Pivetta wrote:
> On Tue, Jan 17, 2017 at 5:35 PM, Stanislav Malyshev
> wrote:
>
>> What prevents you from being able to create proper issues on bugs.php.net?
>
> Nothing: it's just a forgotten corner of the web, like our Jira was.
Why not put a link to bugs.php.net in
Hi All.
Am 17.01.17 um 17:51 schrieb Christoph M. Becker:
> On 17.01.2017 at 17:35, Stanislav Malyshev wrote:
>
>>> People can now cross-reference issues, discuss, get notifications, and
>>> have some simplified/readable markup.
>>
>> All this, except for markup, is available on bugs.php.net. And
Hi!
> Well, what is missing is a simple means to ping another developer –
> currently the only way to do so is assigning the ticket to them, but
> that's not always appropriate.
True. Should not be hard to implement though I think.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP R
Hi!
> Nothing: it's just a forgotten corner of the web, like our Jira was.
I'm sorry, I don't get this "forgotten corner" thing. What exactly is
missing there - glitter? Celebrity endorsements? We have a fully
functional tool, easy to use and available to anybody that needs it. We
do not have to
On 17.01.2017 at 17:35, Stanislav Malyshev wrote:
>> People can now cross-reference issues, discuss, get notifications, and
>> have some simplified/readable markup.
>
> All this, except for markup, is available on bugs.php.net. And I don't
> think markup is that important - I'm pretty sure one ca
On Tue, Jan 17, 2017 at 5:35 PM, Stanislav Malyshev
wrote:
> What prevents you from being able to create proper issues on bugs.php.net?
>
Nothing: it's just a forgotten corner of the web, like our Jira was.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Hi!
> People can now cross-reference issues, discuss, get notifications, and
> have some simplified/readable markup.
All this, except for markup, is available on bugs.php.net. And I don't
think markup is that important - I'm pretty sure one can discuss bugs in
plain text.
> For the 99% of develo
On Tue, Jan 17, 2017 at 9:19 AM, Joe Watkins wrote:
> > I'm sorry I don't understand this. How bugs.php.net is not open?
>
> I said it is open, but it's not being used, it's not in your face like
> github is for a lot of us, it's in a "dark corner of the internet".
>
We (doctrine project, in thi
Morning Stas :)
> True, but some people can not write an RFC, or not ready to do it,
> however they still can request and discuss features.
They can do that, but they can also start a discussion on internals if they
want to encourage someone else to do their work for them.
The RFC document alrea
Hi!
> A lot of the time a feature request is just not enough; it requires at
> least a good discussion, if not an RFC.
True, but some people can not write an RFC, or not ready to do it,
however they still can request and discuss features.
> That there were feature requests open on bugsnet for mo
On Mon, Jan 9, 2017 at 10:10 AM, Andreas Heigl wrote:
> Hi Jakub.
>
> Am 09.01.17 um 10:59 schrieb Jakub Zelenka:
> > Hi,
> >
> > On Mon, Jan 9, 2017 at 7:25 AM, Remi Collet
> wrote:
> >
> >> Hi,
> >>
> >> Le 08/01/2017 à 07:46, Joe Watkins a écrit :
> >>
> >>> I'd like to hear what others think
On Mon, Jan 9, 2017 at 10:04 AM, Remi Collet wrote:
> Le 09/01/2017 à 10:59, Jakub Zelenka a écrit :
> > Hi,
> >
> > On Mon, Jan 9, 2017 at 7:25 AM, Remi Collet
> wrote:
> >
> >> Hi,
> >>
> >> Le 08/01/2017 à 07:46, Joe Watkins a écrit :
> >>
> >>> I'd like to hear what others think about cleani
Hi Jakub.
Am 09.01.17 um 10:59 schrieb Jakub Zelenka:
> Hi,
>
> On Mon, Jan 9, 2017 at 7:25 AM, Remi Collet wrote:
>
>> Hi,
>>
>> Le 08/01/2017 à 07:46, Joe Watkins a écrit :
>>
>>> I'd like to hear what others think about cleaning up bugsnet, what
>> criteria
>>> we might use for a mass cleanu
Le 09/01/2017 à 10:59, Jakub Zelenka a écrit :
> Hi,
>
> On Mon, Jan 9, 2017 at 7:25 AM, Remi Collet wrote:
>
>> Hi,
>>
>> Le 08/01/2017 à 07:46, Joe Watkins a écrit :
>>
>>> I'd like to hear what others think about cleaning up bugsnet, what
>> criteria
>>> we might use for a mass cleanup.
>>
>>
Hi,
On Mon, Jan 9, 2017 at 7:25 AM, Remi Collet wrote:
> Hi,
>
> Le 08/01/2017 à 07:46, Joe Watkins a écrit :
>
> > I'd like to hear what others think about cleaning up bugsnet, what
> criteria
> > we might use for a mass cleanup.
>
> Big +1 for a mass cleanup.
>
> IMHO all bugs reported against
Morning Remi,
+1 on those criteria and ideas about commenting then closing ...
How long between commenting and closing do you think there should be ?
Kalle is going to get access to the bugsnet box, maybe he could get you
access (if you've time to get directly involved, I super hope you have) ?
Hi,
Le 08/01/2017 à 07:46, Joe Watkins a écrit :
> I'd like to hear what others think about cleaning up bugsnet, what criteria
> we might use for a mass cleanup.
Big +1 for a mass cleanup.
IMHO all bugs reported against PHP < 5.6 could be cleaned.
Perhaps something close to the Fedora bugs pro
Morning Kalle,
> I would like some more statuses for the bug tracker
+1 go for it
Cleanup of code/statuses is also desirable ... and you have volunteered to
do it :D
Cheers
Joe
On Mon, Jan 9, 2017 at 6:40 AM, Kalle Sommer Nielsen wrote:
> Morning Joe
>
> 2017-01-09 7:13 GMT+01:00 Joe Watkins
Morning Joe
2017-01-09 7:13 GMT+01:00 Joe Watkins :
> The problem with accepting feature requests on bugsnet is that, most of the
> time, nobody can implement them because of modern processes.
>
> It's not harmful to us, but it is harmful to the person requesting the
> feature, who is probably ign
Morning Stas,
> I think we have to separate FRs and bugs. Bugs filed against older
> versions (especially ones before 5.5) I'd put into feedback with request
> to retest with more recent version. Feedback bugs would automatically
> expire if no feedback was provided.
This sounds reasonable.
> FR
Hi!
> Some of you may have noticed that a few of us have put considerable effort
> into cleanup of pull requests on github, these are now manageable and I'm
> quite confident that we will be able to merge pull requests in a timely
> manner, and stay on top of it.
I would like to start with a big
Hi!
> I'd even go as far as saying that any bug reported for PHP < 5.6 can be
> marked as "Won't fix". The bugs targeting 5.6 need to be checked whether
> they have a security implication and if not they should be also marked
> as "Won't fix"
Lots of people run 5.5 now. I'd say at least about 2/3
Hi all.
Am 08.01.17 um 11:29 schrieb Nikita Popov:
> On Jan 8, 2017 7:47 AM, "Joe Watkins" wrote:
>
> Morning internals,
[…]
>
> With normal support for 5 ended, now is the perfect time to cleanup
> bugsnet. If we can get the numbers down to something manageable, we have a
> reasonable expectat
Afternoon Nikita,
ACK, we should of course use appropriate status ... I have only closed a
few so far before I thought a discussion is probably in order, so no harm
done.
Cheers
Joe
On Sun, Jan 8, 2017 at 10:29 AM, Nikita Popov wrote:
> On Jan 8, 2017 7:47 AM, "Joe Watkins" wrote:
>
> Morning
On Jan 8, 2017 7:47 AM, "Joe Watkins" wrote:
Morning internals,
Some of you may have noticed that a few of us have put considerable effort
into cleanup of pull requests on github, these are now manageable and I'm
quite confident that we will be able to merge pull requests in a timely
manner, and
Am 08.01.2017 um 07:46 schrieb Joe Watkins:
> I think any bug report opened against 4 and not updated is useless.
+1
> I think anything with a patch attached targeting 5 is useless, regardless
> of age; they should be encouraged to open a pull request on github against
> a supported branch.
+1
Morning internals,
Some of you may have noticed that a few of us have put considerable effort
into cleanup of pull requests on github, these are now manageable and I'm
quite confident that we will be able to merge pull requests in a timely
manner, and stay on top of it.
When it comes to bugsnet,
58 matches
Mail list logo
