normally do not
click links named "50 things that will make you say Oh!" or "You cannot
imagine what will happen at the end of this video". :)
Thanks,
andre (obviously surprise-averse)
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
[3] https://phabricator.wikimedia.org/T95184#1327072
[4] https://phabricator.wikimedia.org/T85140
[5]
https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugzilla_and_RT_accounts
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org
ator's "Search can be improved" as stated in
https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Considerations )
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-
nybody interested could have kept compat (more) alive over the last
years. Or could in the future.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimed
On Wed, 2015-06-10 at 02:01 -0400, MZMcBride wrote:
> a list of a dozen features that are missing (search by file size,
> by color, by image file format, etc.).
Also see https://phabricator.wikimedia.org/T101089 and
https://phabricator.wikimedia.org/T101087
--
Andre Klapper | Wik
list of stuff to look into & think
about, and I'm interested in your thoughts and comments on the current
bug management process.
More news and ideas to come once things are sorted out a bit more. :)
andre
--
Andre Klapper | Wikimedia Bugwrangler
h
into bug
management: Your feedback is very welcome.
No comments means nobody has strong feelings and I'll simply go
ahead. ;)
Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikit
ging and removing duplicated information it
might make sense in some cases to redirect to a generic Bugzilla-related
frontpage on the wiki instead.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
bullet points that seem unclear.
Seems like mediawiki.org will also be the place for the content itself
(with potential interwiki redirects to mw.org).
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l ma
ixable via a bug report as you will never be able to clearly define
when the problem got "fixed".
I recommend discussing on mailing lists / IRC / wikis instead.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
his should be the easiest way to find them.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
hange?
Yes, see
http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
.org/wiki/Bug_management/Wild_ideas
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi,
you can unsubscribe by going to the bottom of
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
and logging in.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitec
se / until resolved" will be hard
(impossible?) to get via functionality provided by the Bugzilla web
interface or XML-RPC. Probably SQL query land instead.
> Could we have something like http://www.octofish.net/bugjar/ ?
Is the script behind that somew
gt;From a quick search in Wikimedia's bugtracker for Gujarati, I found
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=35044,35668,41763
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing l
Hi Harsh,
On Mon, 2012-11-05 at 23:28 +0530, Harsh Kothari wrote:
> Thanks for your response. Now How can I fix this bug?
I recommend to give
http://meta.wikimedia.org/wiki/Wikimedia_developer_hub and
https://www.mediawiki.org/wiki/Developer_hub a read. :)
andre
--
Andre Klapper | Wikime
project uses "RESOLVED WAITING_FOR_UPSTREAM" for this.
If I miss meanings, please provide them.
Currently I'm in favor of killing RESOLVED LATER (which requires
retriaging these tickets) and introducing a RESOLVED
WAITING_FOR_UPSTREAM status for the latter case.
andre
--
Andr
the RESOLVED status, but to me
that's when a mistake has been made (commit didn't fix the issue, etc).
On the contrary, "RESOLVED LATER" sounds like a "resolution" that ALWAYS
has to get reverted... "later".
andre
--
Andre Klapper | Wikimedia Bugwr
On Tue, 2012-11-06 at 14:10 -0800, Quim Gil wrote:
> Andre, I don't think we need a new resolution WAITING_FOR_UPSTREAM.
After reading Krinkle's and your email I agree that there is no urgent
need for it. This could still be reevaluated in the future.
andre
--
Andre Klappe
rts as RESOLVED FIXED via a bot from Gerrit/Git
could also have its cornercases (e.g. merging several patches across
components, support reverting of Git merges by reopening Bugzilla
ticket?, etc.). Would require some thoughts and testing.
andre
--
Andre Klapper | Wikime
es" keyword in their Bugzilla so developers can
mark fixes worth to mention, but obviously not every commit/merge has a
corresponding ticket in the bugtracker (especially in case of
functionality enhancements).
I don't know about the acceptance by developers though (how many are
aware of it
oth cases, but I don't see us
getting all bugs fixed quickly due to missing unlimited manpower. :)
So in case there is a culture in Wikimedia Bugzilla to not use WONTFIX
too often, it could be interesting to discuss its use and the reasons.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
:)
> As for the noisy search results, the problem is
> https://bugzilla.wikimedia.org/show_bug.cgi?id=39644
Fixed now.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@li
hanks a lot in advance!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
oints!
I'll stick to "WONTFIX = we are against fixing this request" now.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
s, reopen them by
setting appropriate values (lowest priority, upstream), and
explain why (pointing to this thread). Help welcome.
Once no RESOLVED LATER tickets remain, I can remove the resolution.
Silence means approval.
andre
--
Andre Klapper | Wikimedia Bugwrangle
press, thanks.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
press.
Thanks.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
color MWExtensions based on a manual list (e.g. "green = deployed")
etc.
Obviously the code could be improved but it "works for me":
https://gerrit.wikimedia.org/r/gitweb?p=wikimedia/bugzilla/triagescripts.git;a=summary
Feedback and contributions welcome.
andre
-
memcached-multiwrite.'
21:54 logmsgbot_: aaron synchronized wmf-config/InitialiseSettings.php
'Disabled spammy (with pecl memcached) memcached.log, the useful one is
memcached-serious.'
Also Reedy mentioned on IRC that "Peter did some bits apaches upgrades
to 12.04 yesterda
every extension, are peple expected to try git master for
the time being?
https://bugzilla.wikimedia.org/show_bug.cgi?id=16424#c3 lists a few
MediaWiki Support Desk postings by people asking how to download
extensions for 1.20. I assume people might stick with 1.19 if there's no
clear message her
On Mon, 2012-11-19 at 16:01 +0100, Bináris wrote:
> What happened to d: interwiki of Wikidata? There are a lot of links using
> it and suddenly all became red.
As per https://bugzilla.wikimedia.org/show_bug.cgi?id=41980#c22 it's
been reverted for the time being.
andre
--
An
following definitions for Priority:
* highest: Needs to be fixed as soon as possible, a week at the
most. A human assignee should be set in the "Assigned to" field.
* high: Should be fixed within the next four weeks.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.
/adblockplus.org/en/bugs
There's a bunch of similar comments already in that forum, like
ymail.com vs gmail.com etc.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wik
On Tue, 2012-11-20 at 02:33 +0100, Andre Klapper wrote:
> == Proposal ==
>
> Proposing the following definitions for Priority:
> * highest: Needs to be fixed as soon as possible, a week at the
> most. A human assignee should be set in the "Assigned to" field.
> *
orked proposal: New "Immediately" priority ==
I propose adding a *new* priority called "Immediate" which should only
be used to mark really urgent stuff to fix. This priority would be added
above the existing "Highest" priority.
[I'm going to respond to
t
"severity" (blocker, critical, ..., trivial, enhancement) in Bugzilla is
supposed to mean.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
t;
and blocker bugs that are all used to somehow express some "ranking of
issues" (to avoid terms like prioritization or severness).
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
On Tue, 2012-11-27 at 17:39 +0100, Andre Klapper wrote:
> I propose adding a *new* priority called "Immediate" which should only
> be used to mark really urgent stuff to fix. This priority would be added
> above the existing "Highest" priority.
1) Look at the current
ow to do software development, some
work well for some, others work well for others, and not every tool is
needed by everybody.
GitHub itself has a bugtracker ("Issues" tab) by the way.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
__
need to be set separately
I agree in the long run, but it might interfere with teams and their use
of Bugzilla again. Global workflows vs. "this works for my team".
Right now I'd like to introduce a clear way to mark issues that should
be handled immediately.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Bugzilla 4.0 currently, and
wikimedia/bugzilla/modifications/bugzilla-4.0/ does not include such a
script.
Does any historian know if it was just forgotten to drop the file in SVN
(now Gerrit) in the "bugzilla-4.0" folder? Mark, maybe?
Thanks,
andre
--
Andre Klapper | Wikimedi
time. Reports should have an assignee set in the
"Assigned to" field.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
0 days?
=> 148 bug reports got opened more than 274 years ago?
But maybe I fail to read weekly-bug-summary.cgi correctly.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech
could they provide?
Obviously I'd love to avoid ending up with the same situation (and
"lively" Village Pump discussions) again tomorrow when deploying wmf5 to
all other Wikipedias.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
_
As announced for several days on bugzilla.wikimedia.org already,
bugzilla.wikimedia.org will be unavailable due to maintenance work on
Tuesday, December 04th from 18:00 UTC until max. 20:00 UTC (10:00 PST -
12:00 PST).
That starts now.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http
global
watchers are CCs so we can use their prefs to for instance ignore
CC-only mails."
New features and improvements of this Bugzilla version:
http://www.bugzilla.org/releases/4.2.4/release-notes.html#v42_feat
Happy bug reporting!
andre
--
Andre Klapper | Wikimedia Bugwrangler
ht
On Tue, 2012-12-04 at 14:53 -0500, Chad wrote:
> On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper wrote:
> > The only (potential) regression is that we did not apply previous
> > changes to Bugmail.pm, described as "Wikimedia Hack! Pretend global
> > watchers are CCs so we
bout bug *fixes* ("RESOLVED FIXED" in Bugzilla terms).
Obviously I exclude any other Bugzilla resolutions here. :)
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, 2012-12-05 at 00:29 +0100, Andre Klapper wrote:
> On Tue, 2012-12-04 at 14:53 -0500, Chad wrote:
> > On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper
> > wrote:
> > > The only (potential) regression is that we did not apply previous
> > > changes to Bugmail
t
to drown in bugmail, and you can use wikitech-l@ as usual.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ser Watching"
list. Then Bugzilla will make you receive the bugmail that such accounts
would theoretically receive. That's all. No email is "physically" sent
to such virtual accounts. That is contrary to wikibugs-l@ which seems to
be an existing and worki
ing it, I'm just trying to understand, and I'm
picking VE as the most recent example.
Thanks in advance for explaining,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@
een Bugzilla and
Gerrit, or automatic status setting in Bugzilla when a patch is in
Gerrit, or somehow distinguishing in Bugzilla between the situations
"fix merged into code repository", "fix released in MW tarball" and "fix
deployed on an MW server". I hereby thank
On Thu, 2012-12-13 at 09:52 -0800, Steven Walling wrote:
> I also got this on attachments last night.
This was https://bugzilla.wikimedia.org/show_bug.cgi?id=43061 and I'm
waiting for an answer by Reedy what the problem was exactly.
andre
--
Andre Klapper | Wikimedia Bugwrang
st *anybody* can easily query the status of a patch in
Gerrit and see that it's rotting. The real status and progress is not
only in somebody's head or on somebody's harddisk.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
__
g this up. As quoted in my initial
posting, see https://bugzilla.wikimedia.org/show_bug.cgi?id=42470#c4 -
some developers want to exclude bug reports from queries when this
reports have a patch for review in Gerrit.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org
https://bugzilla.wikimedia.org/show_bug.cgi?id=43130
I don't have shell access myself.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.
> Bugs REOPENED : 77
> Bugs RESOLVED : 337
FYI, high numbers are likely related to me reopening about 100 tickets
that were previously in RESOLVED LATER state.
andre
--
Andre Klapper | Wi
ally for a patch reviewer feels as
wrong as letting new bug reporters search for an assignee or somebody to
comment on their report.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lis
On Wed, 2012-12-12 at 19:03 +0100, Andre Klapper wrote:
> I'm proposing adding a new status like
> PATCH_TO_REVIEW or
> or something like this (bikeshed, yay!). Probably the first.
> The status would replace the "patch-in-gerrit" keyword
Thanks for the opinions an
ncement requests in https://bugzilla.wikimedia.org against product
"MediaWiki extensions" and component "TimedMediaHandler". Thanks!
andre
[1]
http://blog.wikimedia.org/2012/11/08/introducing-wikipedias-new-html5-video-player/
--
Andre Klapper | Wikimedia Bugwran
us I don't trust the results in this email, in general.
andre
[1]
https://bugzilla.wikimedia.org/buglist.cgi?chfield=[Bug%20creation]&chfieldfrom=-7d&chfieldto=Now&query_format=advanced&order=bug_id
[2]
https://bugzilla.wikimedia.org/buglist.cgi?chfieldto=Now&chfield
would like?
> Can you coordinate with Patrick to figure that out?
In my understanding I wouldn't call performance a product (no
identifiable codebase, hence also the Bugzilla *keyword* across
products) but I see what you mean. :)
I'd also love to see the documentation asked for by Nem
mp;product=Wikimedia%20Labs
> I think what we're mostly missing is a quick list of easy things to do or
> fix as a call to action.
In case there are some open Bugzilla tickets that describe easy things
to fix, please feel free to set the keyword "easy" on them, so potential
ne
tice.
Is there a vague deadline when to have Translate + ULS deployed to all
wikis that currently use Narayam + WebFonts (if that question makes
sense)?
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mai
mp;bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&o1=lessthaneq&resolution=---&chfieldto=1y&query_format=advanced&v1=1
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklappe
ming as we might be busy enough
tracking down problems with the datacenter move. :)
andre
[1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065792.html
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
__
ase, the aforementioned "Bug meeting prep" page links to a "Bug
Triages" calendar on Google Calendar but I have no idea how to edit it,
plus it feels a bit isolated.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
does keep some humans out.
>
> > I don't see how the spambot statement is true. Do you have evidence for it?
>
>
> That spambots get through at all.
Evidence is not provided by simply repeating the statement. :)
"at all" implies that some spambots are blo
media.org/show_bug.cgi?id=5309
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
as both need buy-in
(developers and reporters need to know and remember that QA works on
automated browser tests, and should mark issues accordingly), but
nothing better came to my mind in the last days. :-/
andre
[1↑] or display the buglist embedded in a wiki page, by using something
like htt
[CC'ing wikitech-l@ again]
On Thu, 2013-01-24 at 10:50 -0700, Chris McMahon wrote:
> On Thu, Jan 24, 2013 at 10:30 AM, Andre Klapper
> wrote:
> 1) Bugzilla already has a number of keywords such as
> * need-integration-test (Selenium test should be written f
tps://commons.wikimedia.org/wiki/File:Halfanim.jpg was uploaded Jan15
2013 already and reported by matanya on IRC today.
Help appreciated.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wik
n help and involve others e.g. interesting extensions.
Please help me to better understand this.
Do you maybe have in mind something like "Reports filed in the last four
weeks that have not seen a response yet"? That would make sense.
But really "fresh" bugs need to be triaged o
d on Saturday at 18h, after the sessions?
> >
>
> +1.
Sounds good if we agree on a place to meet (e.g. a booth/stand).
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wiki
Just a reminder: This is now.
Feel free to join #wikimedia-dev , hang out with us, and clean up some
older bug reports that need some love!
andre
On Fri, 2013-01-18 at 14:15 +0100, Andre Klapper wrote:
> Hi everybody,
>
> I am happy to announce and invite you to the next Wikimed
iority" field.
There are still many blank fields and it's work in progress.
I'm sharing it here as it might be useful for others, plus you are of
course welcome to correct or add any data:
https://www.mediawiki.org/wiki/Bug_management/Development_teams_usage
andre
--
An
noukian article) are missing / uninterpreted.
Templates used in the New York article don't include such markup.
Make sure templates are installed and try again? :)
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
W
le extensions" is interpreted by
individuals who once upon a time added that category on an extension
homepage and then forgot about it...
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing l
On Tue, 2013-02-19 at 13:09 -0800, Rob Lanphier wrote:
> I'm excited to welcome Greg Grossmeier as our new Release Manager at
> the Wikimedia Foundation.
Welcome Greg (and see you next week)!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.o
ge full of random characters and boxes). Running
> ?action=purge on them sorted it out, but if he hit upon two corrupted
> pages in a few minutes, there are probably more.
>
> Does anyone know anything about it?
Not without a testcase (URL) to start investigating. :)
andre
--
Andre Klapper
to_report_a_bug a generic, high-level page.
Case-specific debug information is very welcome on a separate page
though (similar to http://www.mediawiki.org/wiki/Manual:How_to_debug for
MediaWiki), and could be linked to from How_to_report_a_bug.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http:
it:
See https://www.mediawiki.org/wiki/Bug_management/Triage/20130318
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
rge: http://sourceforge.net/projects/icinga/.
>
> I can't find the bug tracker, but it's early and I haven't had any caffeine.
It's located at https://dev.icinga.org/projects/icinga-core/issues
I've added it to
https://www.mediawiki.org/wiki/Bug_management
> Where is this reported in Bugzilla?
https://bugzilla.wikimedia.org/show_bug.cgi?id=43594
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Sat, 2013-03-02 at 16:47 -0300, Helder . wrote:
> Can we get the "owner" instead of the "last reviewer" in the text
> below, when a change is merged?
Please file a request under the "Wikimedia" product in
https://bugzilla.wikimedia.org so this does no
verity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&resolution=---&query_format=advanced&component=General%2FUnknown&product=MediaWiki
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
__
On Mon, 2013-01-07 at 12:47 +0100, Andre Klapper wrote:
> On Mon, 2013-01-07 at 09:25 +0100, Siebrand Mazeland (WMF) wrote:
> > Does this report contain any data that can actually be trusted? Is anyone
> > getting anything useful out of this report?
Again thanks Siebrand for
m how to
make Bugzilla better.
andre
[1] https://meta.wikimedia.org/wiki/IRC_office_hours
[2] https://bugzilla.wikimedia.org
[3] https://www.mediawiki.org/wiki/Bug_management
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/akl
people to not use the same email addresses in Gerrit
and Bugzilla (→ setting assignee).
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
we actually use.
TODO: I don't trust that query yet, numbers feel too high.
> Created reports per component
[...]
> Created reports per product
Results now include ALL reports filed in the last 7 days no matter which
current status they have. Previously only cov
Thread:Talk:Bug_management/How_to_triage/WONTFIXing
Meaning of WONTFIX was discussed in
http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064357.html
so I've adjust my interpretation to "we are against fixing this".
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.
"
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
t; queries, enabling the "Show in
Footer" checkbox, and clicking the "Submit Changes" button at the
bottom.
Obviously there are still several open policy questions to sort out, but
we've got to start somewhere.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Mon, 2013-03-11 at 17:09 +0100, Christian Aistleitner wrote:
> On Mon, Mar 11, 2013 at 12:43:44AM +0100, Andre Klapper wrote:
> > Are there some thoughts already how to make a match between a
> > project in Gerrit and its related Bugzilla product/component?
> > [Disclaim
t, so if you want to make sure to only find your own
entries again I highly recommend using some namespace for your entries.
I use the whiteboard to add "aklapper-moreinfo" entries whenever I would
set a "this report needs more info" flag or status in other Bugzillas.
andre
--
A
-l/2013-February/066847.html
> [5] https://www.mediawiki.org/wiki/QA/Weekly_goals
> [6] http://etherpad.wmflabs.org/pad/p/BugTriage
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Andre
hour next month.)
andre
On Thu, 2013-03-07 at 14:41 +0100, Andre Klapper wrote:
> Hi everybody,
>
> on Tuesday 19th 17:00 UTC[1], there will be an IRC Office Hour in
> #wikimedia-office about Wikimedia's issue tracker[2] and Bug
> management[3].
>
> Add it to your
201 - 300 of 689 matches
Mail list logo