517:
117:
107:
242:
triggered ParserFunction bugs on both nl.wikipedia.org and eo.wikipedia.org. The traffic from nl.wikipedia.org was enough at the time to cause a noticeable spike in CPU usage on the web servers, including some time-out errors; thus, deployment onto nl.wikipedia.org had to be delayed. After these issues are resolved , the second wave of deployment is expected to start on
Wednesday, February 16 (see the
33:
127:
87:
137:
97:
216:
been waiting for review for a long time. The
Foundation’s big contribution to the release was the ResourceLoader, a piece of MediaWiki infrastructure that allows for on-demand loading of JavaScript. Many other incremental improvements were made in how MediaWiki parses and caches pages and page fragments.
357:
and custom interfaces to create WikiProject-sized "forks" as the key to the long-term survival of the project, arguing that community decentralization would create smaller, more manageable and more welcoming groups of editors. Laugher compares these to the editing groups that existed at the beginning
198:
to even outage for some users. At this point, the deployment was rolled back to the previous 1.16 release. The tech team investigated and prepared for another attempt after resolving some technical issues. A second attempt was made at 16:27 UTC, but this ran into similar performance issues and had to
225:
After further investigation and several fixes to the release, Rob
Lanphier, a developer with the WMF, added that "some of the unsolved issues are complicated enough that the only timely and reasonable way to investigate them is to deploy and react". As a result of this, he said, a new plan had been
237:
some old code for project-wise upgrading). The first phase took place 6:00–12:00 UTC on Friday, February 11. This was limited to the Simple
English Knowledge (XXG) and Wiktionary; the Usability and Strategy Wikis; Meta; the Hebrew Wikisource; the English Wikiquote, Wikinews and Wikibooks; the Beta
215:
The 1.17 release process has been longer than we would have liked, which has meant more code to review, and more likelihood for accumulating a critical mass of problems that would cause us to abort a deployment.... was an omnibus collection of fixes, including a large number of patches which had
241:
At the time of writing, the deployment had been completed on all but the last two projects. The Hebrew
Wikisource, included after a request from a community member, gave a chance to observe the deployment on a right-to-left language wiki. The team also reported some localization issues which
226:
drawn up in which 1.17 will be deployed on "just a few wikis at a time". The tech team believes the problem was located in the configuration of the $ wgCacheEpoch variable, which caused a more aggressive culling of the cache than the servers could handle (
260:
with some existing
Javascript code. Trevor Parscal and Roan Kattouw, the main developers of the ResourceLoader, were available on IRC on February 14 at 18:00 (UTC) to answer queries related to the new feature.
561:
193:
servers, which are responsible for delivering content to users, became overloaded and started behaving unpredictably. The increased load culminated with multiple issues across the project from increased
566:
556:
504:
495:
174:
461:(female user) on the German Knowledge (XXG)—had come up in the recent discussions about Knowledge (XXG)'s "gender gap", where it was criticized as "hardcoded discrimination" and Sue Gardner had
541:
73:
551:
546:
534:
373:
450:
295:
528:
52:
41:
279:
685:
21:
660:
655:
650:
337:
One of the applications of a defined parser grammar would be the ability to have alternative, non-MediaWiki interfaces to interact with the content. The
328:
416:, has been in the works for a while, having been mentioned in the last three WMF Engineering Updates. Its relationship with previous monitoring tools
312:
645:
257:
254:
640:
516:
46:
32:
17:
169:
The planned update of MediaWiki as the underlying software which forms the basis of WMF wikis to version 1.17 failed last week (
629:
377:
363:
409:
270:
Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for many weeks.
218:
211:
369:
401:
324:
441:(opened January 2009) allows for the display of namespace aliases in userpages to be gender-specific (revision #
350:
666:
287:
203:
308:
408:
to allow staff, community members and the general public to keep an eye on the servers' uptime and status (
283:
320:
425:
484:
381:
358:
of
Knowledge (XXG), and those that can still be found in various specialized wikis (most notably
190:
181:), but preparations took longer than anticipated and actual deployment began at around 13:00 UTC.
469:
438:
90:
473:
442:
346:
120:
480:
462:
286:
a default feature on the
English Knowledge (XXG). Implementation discussion is proceeding at
100:
250:
130:
391:
206:
about the failed deployment and explained what the
Foundation had attempted to deploy:
150:
253:
Q&A was held on matters related to the
ResourceLoader, which is expected to cause
679:
342:
170:
227:
110:
140:
316:
154:
451:
Widespread discussions about the low participation of women in Knowledge (XXG)
173:). The original deployment was expected to begin 07:00 UTC on February 8 (see
354:
483:(opened January 2007) was closed successfully, after the introduction of
476:, allowing the direct linking to sections (tabs) of the preferences page.
234:
189:
miss rate almost doubled with the new deployment, at which point the
372:
to wikis, to allow easy forking and merging (a concept explored in
233:
The team decided on a two-stage deployment for their next attempt (
199:
be called off 90 minutes later. Further attempts were put on hold.
368:
The talk also examined the possible application of the concept of
359:
186:
307:
After the last attempt at creating a wikitext parser generated
51:
338:
243:
208:
195:
185:
Several issues became apparent almost immediately. The parser
413:
515:
362:). Similar ideas have been floating around for a while; see
31:
353:) that touched on the subject. She proposes the use of the
301:
on RefTools/RefToolbar and other references-related tools).
453:"), the blanket use of masculine namespace forms—such as
282:, it was decided by near unanimous consensus to make the
613:
601:
594:
582:
487:
allowed easy customisation of MediaWiki sites' footers.
323:
under the name of "Kiwi". Discussion is ongoing in the
625:
Get the latest headlines on your user page – just add
238:
Wikiversity; and the Esperanto and Dutch Wikipedias.
202:
Danese Cooper, Wikimedia's Chief Technical Officer,
599:If your comment has not appeared here, you can try
315:on the wikitext-l mailing list, a new attempt, by
421:
417:
405:
341:was released of "Distributed wikis", a talk at
246:of WMF wikis that are already running 1.17).
8:
434:Several long-standing bugs have been fixed:
290:, and the switch is currently on hold until
68:Bugs, Repairs, and Internal Operational News
610:No comments yet. Yours could be the first!
686:Knowledge (XXG) Signpost archives 2011-02
394:was made on the wikitech-l mailing list.
18:Knowledge (XXG):Knowledge (XXG) Signpost
602:
586:
294:is deployed (see also last September's
67:
472:(opened October 2008) was resolved in
7:
364:meta:Versioning and distributed data
319:developer Karl Matthias, has been
53:
28:
400:The WMF announced that a public
135:
125:
115:
105:
95:
85:
595:add the page to your watchlist
398:Public status-monitoring page:
1:
437:The successful close of bug #
370:distributed revision control
164:deployment failed, postponed
412:). The service, powered by
406:http://status.wikimedia.org
702:
374:various earlier proposals
355:write function of the API
457:(male user) rather than
404:page has been set up at
384:in software development.
288:MediaWiki talk:Common.js
280:poll at the Village Pump
520:
36:
630:Signpost-subscription
519:
508:"Technology report" →
449:reported last week ("
35:
592:To follow comments,
345:by Brianna Laugher (
305:New wikitext parser?
562:Features and admins
500:"Technology report"
587:Discuss this story
567:Arbitration report
557:WikiProject report
521:
335:Distributed wikis:
313:lengthy discussion
228:Wikimedia Techblog
171:Wikimedia Techblog
42:← Back to Contents
37:
603:purging the cache
572:Technology report
402:status monitoring
378:Flagged revisions
347:User:pfctdayelise
276:RefTools default:
223:
222:
65:Technology report
47:View Latest Issue
693:
669:
634:
628:
606:
604:
598:
585:
539:
531:
529:14 February 2011
524:
507:
499:
382:release versions
376:), and compared
321:brought to light
209:
182:
157:
139:
138:
129:
128:
119:
118:
109:
108:
99:
98:
89:
88:
59:
57:
55:
54:14 February 2011
701:
700:
696:
695:
694:
692:
691:
690:
676:
675:
674:
673:
672:
671:
670:
665:
663:
658:
653:
648:
643:
636:
632:
626:
622:
621:
616:
614:+ Add a comment
611:
608:
600:
593:
590:
589:
583:+ Add a comment
581:
577:
576:
575:
532:
527:
525:
522:
511:
510:
505:
502:
497:
485:$ wgFooterIcons
388:Call for skins:
325:post's comments
284:refTools gadget
267:
251:IRC office hour
168:
166:
158:
148:
147:
146:
145:
136:
126:
116:
106:
96:
86:
80:
77:
66:
62:
60:
50:
49:
44:
38:
26:
25:
24:
12:
11:
5:
699:
697:
689:
688:
678:
677:
664:
659:
654:
649:
644:
639:
638:
637:
624:
623:
620:
619:
618:
617:
612:
609:
591:
588:
580:
579:
578:
574:
569:
564:
559:
554:
549:
544:
542:News and notes
538:
526:
514:
513:
512:
503:
494:
493:
492:
491:
490:
489:
488:
477:
474:revision 81573
466:
429:
410:Wikimedia blog
395:
392:call for skins
385:
367:
332:
302:
292:MediaWiki 1.17
266:
263:
221:
220:
217:
213:
165:
162:MediaWiki 1.17
159:
144:
143:
133:
123:
113:
103:
93:
82:
81:
78:
72:
71:
70:
69:
64:
63:
61:
58:
45:
40:
39:
30:
29:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
698:
687:
684:
683:
681:
668:
662:
657:
652:
647:
642:
631:
615:
605:
596:
584:
573:
570:
568:
565:
563:
560:
558:
555:
553:
552:Accreditation
550:
548:
545:
543:
540:
536:
530:
523:In this issue
518:
509:
501:
486:
482:
478:
475:
471:
467:
464:
460:
456:
452:
448:
444:
440:
436:
435:
433:
430:
427:
423:
419:
415:
411:
407:
403:
399:
396:
393:
389:
386:
383:
379:
375:
371:
365:
361:
356:
352:
348:
344:
343:linux.conf.au
340:
336:
333:
330:
329:on wikitext-l
326:
322:
318:
314:
310:
306:
303:
300:
298:
293:
289:
285:
281:
277:
274:
273:
272:
271:
264:
262:
259:
256:
255:compatibility
252:
247:
245:
239:
236:
231:
229:
214:
210:
207:
205:
200:
197:
192:
188:
183:
180:
178:
172:
163:
160:
156:
152:
142:
134:
132:
124:
122:
114:
112:
104:
102:
94:
92:
84:
83:
75:
56:
48:
43:
34:
23:
19:
571:
535:all comments
458:
454:
447:The Signpost
446:
431:
397:
387:
334:
304:
296:
291:
275:
269:
268:
248:
244:current list
240:
232:
224:
201:
184:
176:
167:
161:
667:Suggestions
547:In the news
317:AboutUs.org
459:Benutzerin
432:Bug fixes:
414:Watchmouse
339:full video
309:excitement
278:Through a
79:Share this
74:Contribute
22:2011-02-14
661:Subscribe
463:called it
424:is still
175:previous
151:Theo10011
680:Category
656:Newsroom
651:Archives
498:Previous
465:"awful".
455:Benutzer
351:abstract
299:dispatch
297:Signpost
265:In brief
235:reviving
179:coverage
177:Signpost
121:LinkedIn
101:Facebook
20: |
426:unclear
422:Ganglia
204:blogged
111:Twitter
445:). As
418:Nagios
360:wikias
258:issues
191:Apache
155:Waldir
131:Reddit
91:E-mail
646:About
479:Bug #
470:16013
468:Bug #
443:82029
439:17160
187:cache
16:<
641:Home
506:Next
481:8680
420:and
327:and
311:and
230:).
153:and
141:Digg
380:to
249:An
196:lag
149:By
76:—
682::
633:}}
627:{{
496:←
390:A
349:;
219:”
212:“
635:.
607:.
597:.
537:)
533:(
428:.
366:.
331:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
