> 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
Hi!
It might just be an illusion, but it feels like all three projects have
a lot more resources to spend on all this than PHP does; Rust has
"Working Groups", Kubernetes has "Special Interest Groups", and PHP
struggles to assign each module a single maintainer. How that affects
our tooling
On 09/05/2021 16:30, Max Semenik wrote:
Lots of large projects use GitHub for bug tracking: Go, Rust,
Kubernetes - seems to work well enough for them.
Those three look like good examples in terms of volume. It's hard to
tell from the outside if people are happy with their processes, but we
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
> >
On Sun, May 9, 2021 at 11:58 AM Rowan Tommins
wrote:
> Can we do a throwaway import of a few hundred bugs to a test repo, and see
> what that might look like?
Is there a dump of public issues available somewhere?
The closest to sufficient data export I can find is e.g.
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
On Sun, 9 May 2021 at 16:04, Christoph M. Becker wrote:
>
> I suggest to replace libjpeg[1] with libjpeg-turbo[2] for future PHP
> releases on Windows, starting with PHP 8.1.
>
> Thoughts? Objections?
So the ABI break would only affect people who have some C code that is
dependent on the new
On Sun, May 9, 2021 at 11:58 AM Rowan Tommins
wrote:
> This is my instinct as well - Github Issues seems to be adequate as a
> lightweight bug tracker, but how well will it scale, and how much will we
> miss "advanced" features like separately searchable and reportable fields
> and statuses?
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
Hi all,
I suggest to replace libjpeg[1] with libjpeg-turbo[2] for future PHP
releases on Windows, starting with PHP 8.1. The main reason is that
libjpeg-turbo offers better performance, because it uses SIMD
instructions on supported platforms (Windows x86 and x64 are supported).
Note that many
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.
>
>
On 09/05/2021 09:05, Stanislav Malyshev wrote:
I don't see how we could "just move" if all our bug handling would be
wired into Github. I can easily see how we could move a repo to any
provider that supports git - git is a generic platform, Github is just a
frontend. But there's no alternative
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 bug management system. It's hard to
>fault them as it's not
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
Hi all,
I shouldn't have said we can "just" move ... I'm not supposing it will be
easy.
We can "just move", in about the same sense that we can "just move" today.
Considering the difficulty of problems we do not currently have is a waste
of time.
Cheers
Joe
On Sun, 9 May 2021 at 10:08,
Hey folks:
Am 09.05.21 um 09:33 schrieb Stanislav Malyshev:
> Hi!
>
[...]
>
> 1. Bug reporting templates> 2. Pre-filter on reported bugs> 3. Advanced search
> 4. Custom fields like PHP version or CVE ID
> 5. Private bugs that are accessible only to members of security team
> 6. Custom statuses
Hi!
If at some time in the future, github becomes a less than suitable
environment for us, we can just move, no problem. There's no sense in
which we are locked into anything.
I don't see how we could "just move" if all our bug handling would be
wired into Github. I can easily see how we
Hi Stas,
I did mention that we're leaving aside the sec issue for now.
> Let me list all it is lacking that
we have right now, with current old and dusty bugs:
1)
Am 09.05.2021 um 09:33 schrieb Stanislav Malyshev:
1. Bug reporting template
GitHub Issues has support for reporting templates.
For instance, clicking "New issue" on
https://github.com/symfony/symfony/issues will lead to you
https://github.com/symfony/symfony/issues/new/choose. This is an
Hi!
Quite aside from spam problems, bugsnet is hidden away in a dark corner
of the internet that requires a special login, doesn't integrate with
source code or our current workflow (very nicely), and doesn't get
updated or developed.
Having moved our workflow to github, now seems to be the
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
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
23 matches
Mail list logo
