Id be careful about using numbers in triage right now. The numbers are a
little misleading as the error logging is only enabled on smaller wikis.
Also if an error results in data loss but only impacts a small amount of
people I would say that's worse than a benign error that occurs for lots.
We
Speaking specifically about the new JavaScript error logging, and
specifically to Alex's point about triaging these tasks, it would be very
helpful if the reports included some indication of how often the error is
occurring.
For example, VisualEditor is loaded several hundred thousands times per
ACN -- for what it's worth, I've been working for the foundation for a
while now, and I can report from the inside that the trend is definitely in
a positive direction. There is a lot more internal focus on addressing
code debt and giving maintenance a fair spot at the table. (In fact, my
entire
There is an impression among many community members, myself included,
that Foundation development generally prioritizes new features over
fixing existing problems. Foundation teams will sprint for a few
months to put together a minimum viable product, release it, then move
on to the new hotness,
>
> For example, of the 30 odd backend errors reported in June, 14 were still
> open a month later in July [1], and 12 were still open – three months later
> – in September. The majority of these haven't even yet been triaged,
> assigned assigned or otherwise acknowledged. And meanwhile we've got
On Tue, Sep 15, 2020 at 11:06 AM Brennen Bearnes wrote:
> On 9/15/20 9:43 AM, Alex Ezell wrote:
> > Do we use levels for any of these error log outputs? That is, are they
> > classified on output as High, Medium, Low, Info, or something like that?
>
> Teasing out more detail about reported error
On Tue, Sep 15, 2020 at 10:00 AM Niklas Laxström
wrote:
> ma 14. syysk. 2020 klo 23.49 Tyler Cipriani (tcipri...@wikimedia.org)
> kirjoitti:
> > The number of new tasks being created with this tag in a given week is
> > outpacing the number of tasks being closed in a given week: this past
> >
On 9/15/20 9:43 AM, Alex Ezell wrote:
Do we use levels for any of these error log outputs? That is, are they
classified on output as High, Medium, Low, Info, or something like that?
To an extent, yes. We have separate channels for PHP errors and
exceptions, for example, and although I don't
Hi y'all,
Do we use levels for any of these error log outputs? That is, are they
classified on output as High, Medium, Low, Info, or something like that?
Or do we have to triage each of them as we examine them?
I was just thinking if they were somehow leveled, we could use measurements
of the
On Tue, Sep 15, 2020 at 5:24 AM Derk-Jan Hartman
wrote:
>
> In particular I count 13 frontend problems with the old TMH kaltura player.
> There is clearly no intent to fix those (volunteer or employee), as the
> Kaltura player has been unmaintained for 8 years.
> The choices as far as I can tell
Hi!
Thanks for the feedback, this is useful information.
On Tue, Sep 15, 2020 at 3:00 AM Niklas Laxström
wrote:
> ma 14. syysk. 2020 klo 23.49 Tyler Cipriani (tcipri...@wikimedia.org)
> kirjoitti:
> If there is an increase in the amount of real new issues and/or
> decrease in the amount of
In particular I count 13 frontend problems with the old TMH kaltura player.
There is clearly no intent to fix those (volunteer or employee), as the
Kaltura player has been unmaintained for 8 years.
The choices as far as I can tell are to ignore them, undeploy a/v playback
or to direct C-level
ma 14. syysk. 2020 klo 23.49 Tyler Cipriani (tcipri...@wikimedia.org) kirjoitti:
> The number of new tasks being created with this tag in a given week is
> outpacing the number of tasks being closed in a given week: this past
> week we added 41 tasks and only closed 22.
Majority of the recently
13 matches
Mail list logo
