Sumana Harihareswara wrote:
> Is there already a ticket somewhere in RT or the like re upgrading
> bugzilla.wikimedia.org to 4.2?
https://bugzilla.wikimedia.org/show_bug.cgi?id=33158
MZMcBride
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.or
On 05/07/2012 04:39 AM, Krinkle wrote:
> On Fri, May 4, 2012 at 7:29 AM, Antoine Musso wrote:
>
>> One could most probably write a ton of reports using the JSON API:
>>
>> https://bugzilla.wikimedia.org/jsonrpc.cgi
>>
>> Doc:
>>
>> https://bugzilla.wikimedia.org/docs/en/html/api/Bugzilla/WebServ
On Fri, May 4, 2012 at 7:29 AM, Antoine Musso wrote:
> One could most probably write a ton of reports using the JSON API:
>
> https://bugzilla.wikimedia.org/jsonrpc.cgi
>
> Doc:
>
> https://bugzilla.wikimedia.org/docs/en/html/api/Bugzilla/WebService/Server/JSONRPC.html
>
>
>
Yep, however current
Le 04/05/12 00:14, MZMcBride a écrit :
> This appears to mostly be an index of Bugzilla search queries. Do you know
> if there's been any progress on making the Bugzilla database available in a
> replicated form (on the Toolserver or Wikimedia Labs or elsewhere)? Direct
> SQL access would allow for
On Fri, May 4, 2012 at 8:14 AM, MZMcBride wrote:
> Nice job on this. :-)
>
> This appears to mostly be an index of Bugzilla search queries. Do you know
> if there's been any progress on making the Bugzilla database available in a
> replicated form (on the Toolserver or Wikimedia Labs or elsewhere)
Krinkle wrote:
> Now that we're on a more regular deployment schedule, staying on top of the
> blocking bugs and deviding lists into smaller, more managable chunks, is more
> and more important.
>
> For that reason I put together a quick tool:
>
> https://toolserver.org/~krinkle/wmfBugZillaPortal
On Wed, May 2, 2012 at 8:28 PM, Krinkle wrote:
> https://toolserver.org/~krinkle/wmfBugZillaPortal/
Oooo, nice, thanks for this Krinkle!
Rob
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikite
On May 3, 2012, at 5:28 AM, Krinkle wrote:
> Hey all,
>
> Now that we're on a more regular deployment schedule, staying on top of the
> blocking bugs and deviding lists into smaller, more managable chunks, is more
> and more important.
>
> For that reason I put together a quick tool:
>
> https: