Book tool/Schedule

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

Past and unapproved but possible dates for deployment on various wikis. You can see the complete list of wikis where it's enabled here (warning, huge page!): search "wmgUseCollection".

> 19 Feb 2009[edit]

  • ru.wikipedia.org
  • sv.wikipedia.org
  • tr.wikipedia.org
  • cs.wikipedia.org
  • eo.wikipedia.org (1 message missing)
  • uk.wikipedia.org (1 message missing)
  • sk.wikipedia.org (1 message missing)
  • no.wikipedia.org (1 message missing)
  • hu.wikipedia.org (1 message missing)
  • hr.wikipedia.org (1 message missing)
  • el.wikipedia.org (1 message missing)
  • fi.wikipedia.org (3 messages missing)
  • it.wikipedia.org (3 messages missing)
  • sl.wikipedia.org (6 messages missing)


  • da.wikipedia.org (90 messages missing)
  • ro.wikipedia.org (67 messages missing)
  • bg.wikipedia.org (52 messages missing)
  • ca.wikipedia.org (78 messages missing)
  • lt.wikipedia.org (76 messages missing)
  • sr.wikipedia.org (sr-ec 80 messages missing)
  • et.wikipedia.org (71 messages missing)

Missing localized messages as reported by betawiki on Feb 24th.

24 Feb 2009[edit]

  • en.wikipedia.org limited to logged on users

20 April 2009[edit]

  • en.wikipedia.org

25 August 2009[edit]

  • ms.wikipedia.org

?[edit]

  • lb.wikipedia.org
  • ko.wikipedia.org

6 May 2010[edit]

The book creation tool will be enabled for anonymous English Wikipedia users at 3pm CEST (6am PDT) on May 6.

Dependencies[edit]

Code review[edit]

"Using local storage in Collection extension to work around short-lived sessions #539
The main change is in r65566 but there were some refactorings beforehand and some fixes afterwards in the changesets r65564..r65569.
Minor usability fixes
r65267, r65312, r65377

Additional PDF server[edit]

Resloved - will be in place.

Required resources at the date of enabling:[edit]

  • Tech team member to switch the config option to allow access for anons
  • Tech team member to monitor system load
  • PediaPress developers to provide hotfixes (just in case)
  • Tech team members to review and deploy hotfixes (just in case)