90:
465:
117:
107:
188:. Although these issues were soon fixed, users were also riled by a bug with the Vector-style edit toolbar when it was re-enabled for editors who had previously tried to turn it off. On this issue, developer Roan Kattouw said that he "apologized for messing up" and explained that the temporary loss of this preference setting was the lesser of two evils. "There are about 4,200 affected users on English Knowledge, if memory serves," he added (
33:
127:
87:
137:
97:
262:
The solution I'm proposing is that we branch 1.18 immediately after the release of the 1.17 tarball . Revisions on the trunk could be merged to the 1.18 branch. Or, to make merging into 1.18 less of a chore for a single person, we could enable those doing code review to merge code they've reviewed
183:
The anecdotal evidence coming from users is that page loading times have indeed been reduced by the new
ResourceLoader as hoped. However, many of the issues wikis are now facing were also related to this change: as expected, it broke a number of JavaScript gadgets, including popular scripts such as
301:
If we want to move to continuous integration (and I think the consensus is we do, considering the mess we've made for ourselves by deploying 9 months worth of commits and not knowing which of the ~15,000 new revisions killed the cluster the other day), our first step should be to get closer to
530:
302:
continuous integration, i.e. bring deployment closer to trunk . By the time we deploy 1.17, trunk will already be more than two months ahead... Stabilizing and deploying 1.18wmf1 should take considerably less time and allow us to get much closer to a continuous integration model.
227:
We still have some deployment work left to do... we also want to reintroduce the category improvements that Aryeh Gregor made last summer,... plan to update
ArticleFeedback now that we’re on the newer codebase, and we’ll probably also update some other extensions, too.
110:
199:
parser refused to accept a number of images it had previously allowed, resulting in a loss of thumbnails. Some were soon fixed with a change to the parser (being incorrectly failed); others still need to be fixed manually as they have invalid
130:
100:
140:
292:-style system (where all developers submit patches, rather than adding their changes to the global codebase immediately) might be a better step. Developer Roan Kattouw expanded on Mark Hershberger's more modest proposal:
176:), the latest edition was deployed once more to Wikimedia sites on February 16. Although a number of relatively significant problems soon appeared, these were regarded as fixable without the need for a retreat to 1.16 (
567:
I took the liberty of editing the section about how server load was cut in half to reflect the reality that only 4 servers had their load cut in half, not all of our 100+ Apaches as the wording suggested
215:), was soon reverted locally on the English Knowledge and several other wikis; the change, which was supposed to make the box visually more similar to the Vector skin, may still be reverted globally.
341:), even if these were empty, and attached timestamps to user JS and CSS, thus bypassing the caches, even if a user is logged out and does not have user JS or CSS. Developer Roan Kattouw fixed (
242:
With the deployment to WMF wikis of MediaWiki 1.17, developer attentions have begun to turn towards the strategy for MediaWiki 1.18. Mark
Hershberger, developer and interim bugmeister (cf.
73:
545:
509:
514:
504:
120:
452:
443:
281:
277:
243:
209:
170:
597:
160:
489:
577:
494:
482:
499:
476:
52:
41:
586:
Thank you for making the wording clear! It's still very impressive that this bug fix made such a big difference on resource loader server load. --
663:
550:
67:
557:
237:
21:
638:
534:
633:
628:
422:
occurred when WikiEditor automatically falls back to the classic editor, and the toolbar buttons failed in IE6 . Fixed in
317:
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.
177:
400:
involved
Special:Import ignoring the destination namespace and providing the incorrect source in logs. Fixed in commit
623:
208:, and, in the worst case, security holes. A change in the color of the "New messages" box from orange to blue (cf.
325:
on wikitech-l of critical bugs to work on over the weekend and fix before a MediaWiki 1.17 tarball is released.
411:
caused RSS/Atom feeds of user contributions to break due to the deletedOnly parameter in the link. Fixed in
328:
618:
464:
46:
32:
17:
180:). There was only a partial recurrence of the load spikes seen with the previous attempts at deployment.
350:
430:
419:
408:
397:
386:
375:
364:
334:
263:
into the 1.18 branch. In this way, we achieve Roan's (and my) goal of continuous integration .
349:) the bug, and with the fix, cut load to the 4 Apache servers serving ResourceLoader in half.
322:
644:
389:
occurred when using relative paths in CSS imports, causing CSS to break. Fixed with commit
8:
338:
250:
218:
Developer Rob
Lanphier explained where the development team was going to go from here:
573:
541:
285:
284:) and this week proved no exception. Discussions included a debate of the merits of
354:
311:
169:
1.17 on 8 February 2011, which were quickly reverted on performance grounds (cf.
592:
150:
657:
569:
189:
185:
434:
423:
412:
401:
390:
379:
368:
346:
342:
337:, a ResourceLoader bug that attached a timestamp to site JS and CSS (e.g.
321:
Early on
Saturday, 19 February 2011, bugmeister Mark Hershberger posted a
249:), outlined his views on where MediaWiki development should go from here (
205:
433:
caused the "Stub size threshold" in preferences to not work. Fixed in
587:
166:
154:
195:
Other issues were equally temporary. For example, the new stricter
289:
288:
as the best version control software to be used, and whether a
201:
196:
359:
Over the weekend, the following other bugs were fixed:
378:); A fix was committed and deployed on 19 February in
272:
The issue has been a hot topic in recent months (cf.
374:
With the 1.17wmf deploy, LocalisationUpdate failed (
555:If your comment has not appeared here, you can try
655:
161:MediaWiki 1.17 deployed to sites; initial strife
148:
68:Bugs, Repairs, and Internal Operational News
558:
204:which results in discrepancies between
14:
656:
51:
294:
255:
220:
664:Knowledge Signpost archives 2011-02
165:After the attempted deployments of
27:
463:
363:The edit screen autoscrolling bug
53:
31:
28:
675:
540:These comments are automatically
367:that occurred in IE8 is fixed in
238:Developer attention turn to 1.18
135:
125:
115:
105:
95:
85:
613:: doing it for free since 2005.
551:add the page to your watchlist
13:
1:
598:05:58, 24 February 2011 (UTC)
578:19:17, 22 February 2011 (UTC)
329:Load on 4 servers cut in half
526:
276:coverage from October 2010:
18:Knowledge:Knowledge Signpost
7:
10:
680:
251:Wikitech-l mailing list
548:. To follow comments,
468:
190:Technical Village Pump
36:
467:
456:"Technology report" →
35:
544:from this article's
333:P.Copp reported bug
510:Features and admins
448:"Technology report"
339:MediaWiki:Common.js
535:Discuss this story
515:Arbitration report
505:WikiProject report
469:
178:Wikimedia Techblog
42:← Back to Contents
37:
596:
559:purging the cache
520:Technology report
309:
308:
270:
269:
235:
234:
65:Technology report
47:View Latest Issue
671:
647:
590:
562:
560:
554:
533:
487:
479:
477:21 February 2011
472:
455:
447:
295:
256:
221:
157:
139:
138:
129:
128:
119:
118:
109:
108:
99:
98:
89:
88:
59:
57:
55:
54:21 February 2011
679:
678:
674:
673:
672:
670:
669:
668:
654:
653:
652:
651:
650:
649:
648:
643:
641:
636:
631:
626:
621:
614:
606:
605:
564:
556:
549:
538:
537:
531:+ Add a comment
529:
525:
524:
523:
480:
475:
473:
470:
459:
458:
453:
450:
445:
357:
355:Other bug fixes
331:
314:
240:
163:
158:
147:
146:
145:
136:
126:
116:
106:
96:
86:
80:
77:
66:
62:
60:
50:
49:
44:
38:
26:
25:
24:
12:
11:
5:
677:
667:
666:
642:
637:
632:
627:
622:
617:
616:
615:
608:
607:
604:
603:
602:
601:
600:
581:
580:
539:
536:
528:
527:
522:
517:
512:
507:
502:
497:
492:
490:News and notes
486:
474:
462:
461:
460:
451:
442:
441:
440:
439:
438:
427:
416:
405:
394:
383:
372:
356:
353:
330:
327:
313:
310:
307:
306:
303:
299:
268:
267:
264:
260:
239:
236:
233:
232:
229:
225:
162:
159:
144:
143:
133:
123:
113:
103:
93:
82:
81:
78:
72:
71:
70:
69:
64:
63:
61:
58:
45:
40:
39:
30:
29:
15:
9:
6:
4:
3:
2:
676:
665:
662:
661:
659:
646:
640:
635:
630:
625:
620:
612:
599:
594:
589:
585:
584:
583:
582:
579:
575:
571:
566:
565:
561:
552:
547:
543:
532:
521:
518:
516:
513:
511:
508:
506:
503:
501:
498:
496:
493:
491:
488:
484:
478:
471:In this issue
466:
457:
449:
436:
432:
428:
425:
421:
417:
414:
410:
406:
403:
399:
395:
392:
388:
384:
381:
377:
373:
370:
366:
362:
361:
360:
352:
351:
348:
344:
340:
336:
326:
324:
319:
318:
304:
300:
297:
296:
293:
291:
287:
283:
279:
275:
265:
261:
258:
257:
254:
252:
248:
246:
230:
226:
223:
222:
219:
216:
214:
212:
207:
203:
198:
193:
191:
187:
181:
179:
175:
173:
168:
156:
152:
142:
134:
132:
124:
122:
114:
112:
104:
102:
94:
92:
84:
83:
75:
56:
48:
43:
34:
23:
19:
610:
519:
483:all comments
358:
332:
320:
316:
315:
273:
271:
244:
241:
217:
210:
206:web browsers
194:
182:
171:
164:
645:Suggestions
542:transcluded
495:In the news
500:Versailles
286:Subversion
79:Share this
74:Contribute
22:2011-02-21
639:Subscribe
546:talk page
167:MediaWiki
151:Jarry1250
658:Category
634:Newsroom
629:Archives
611:Signpost
446:Previous
312:In brief
274:Signpost
247:coverage
245:Signpost
213:coverage
211:Signpost
174:coverage
172:Signpost
121:LinkedIn
101:Facebook
20: |
570:Catrope
290:Mozilla
186:Twinkle
111:Twitter
435:r82363
431:#27499
424:r82530
420:#27355
413:r82486
409:#27546
402:r82482
398:#27486
391:r82457
387:#27328
380:r82448
376:#27524
369:r82474
365:#27496
347:r82468
343:r82219
335:#27302
202:syntax
131:Reddit
91:E-mail
624:About
16:<
619:Home
609:The
593:talk
588:Aude
574:talk
454:Next
429:Bug
418:Bug
407:Bug
396:Bug
385:Bug
345:and
323:list
155:Aude
153:and
141:Digg
253:):
197:SVG
192:).
149:By
76:—
660::
576:)
568:--
444:←
305:”
298:“
280:,
266:”
259:“
231:”
224:“
595:)
591:(
572:(
563:.
553:.
485:)
481:(
437:.
426:.
415:.
404:.
393:.
382:.
371:.
282:2
278:1
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.