Hello everyone,
I am happy to announce the availability of the first stable release of the
new MediaWiki 1.25 series.
MediaWiki 1.25 is a large release that contains many new features and bug
fixes. This is a summary of the major changes of interest to users. You can
consult the RELEASE-NOTES-1.25 file for the full list of changes in this
version.
Our thanks to everyone who helped to improve MediaWiki by testing the
release candidates and submitting bug reports.
== What's new for users? ==
MediaWiki 1.25 includes all changes released in the smaller 1.25wmf*
software deployments to Wikimedia sites over six months, totaling
approximately 2200 changes.
* Indicators – Templates that add icons to the top right corner of the page
(and more) can be updated to use the new page status indicators feature.
* Enhanced recent changes – MediaWiki now uses by default the extended
watchlist and so called enhanced recent changes (preference "Group changes
by page in recent changes and watchlist"), which also received several
improvements in MediaWiki 1.24 and 1.25 (task 37785). This means that
Special:RecentChanges and Special:Watchlist show all the changes to each
page in a given day, sorted by page rather than chronologically. Changes to
each page are collapsed by default and a compact overview is shown, with
links to collated diffs and counts of each user's actions. Full activity
for an individual page can then be shown with a single click. Users will no
longer need to know in detail how a single change was chosen for display in
order to figure out what else may have happened to the page that day, nor
to scan a long list of non-contiguous lines on the screen in order to get a
complete picture. The change is part of MediaWiki's evolution towards an
interface which is more discoverable and less cluttered by default, while
equally easy to quickly access in full, with the help of JavaScript.
However, the (grouped) layout is an improvement for non-JavaScript users as
well.
* Live preview – While editing, you're not sure what a wikitext syntax will
produce? That's no longer a problem, now that live preview is no longer
experimental. By enabling the feature in your preferences, MediaWiki will
display the effect of your edits without fully reloading the page, so that
you can quickly correct any mistake.
* Import – The import tool is now much easier to use on content from a wiki
which has different namespaces than yours (e.g. because it's in another
language).
* Internationalization – In logging and gender support, continuing the work
in MediaWiki 1.18 and 1.19, multiple log types of Special:Log have been
migrated to the new logging system, which allows full internationalization
including word order and grammatical gender. The migration continues. See
task T26620 for a list.
Locales – The following locales have been added: अवधी, بلوچی رخشانی and
Koyraboro Senni.
* API documentation is localized and easier to access through
Special:ApiHelp.
== What's new for system administrators? ==
* PHP 5.3.3 is now required (from 5.3.2)
* Extensions and skins are now loaded through a new registration system
* Profiling was completely overhauled to use the xhprof module.
Full release notes:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_25/RELEASE-NOTES…https://www.mediawiki.org/wiki/Release_notes/1.25
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0.tar.gzhttp://download.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0.tar.gz.s…http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
-Chad Horohoe, MW Release Manager
_______________________________________________
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Thank you for the quick fix!
Best,
--
Sukyoung
On Jan 29, 2014, at 9:55 AM, Nathan wrote:
> FYI in case you aren't subscribed to the list.
>
> ---------- Forwarded message ----------
> From: Yair Rand <yyairrand(a)gmail.com>
> Date: Tue, Jan 28, 2014 at 7:25 PM
> Subject: Re: [Wikitech-l] Bug in the Wikipedia main web page
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> Thank you for pointing out this bug. Your suggested change to
> MediaWiki:Gadget-wm-portal.js has been implemented by Meta-Wiki
> administrator User:PiRSquared17.
>
>
> On Tue, Jan 28, 2014 at 6:50 PM, Sukyoung Ryu <sukyoung.ryu(a)gmail.com>wrote:
>
> > Dear all,
> >
> > We are researchers at KAIST in Korea working on finding JavaScript bugs in
> > web pages. While analyzing top websites from Alexa.com, we found an issue,
> > which seems to be a bug, on the Wikipedia main web page (wikipedia.org).
> > We would be grateful if you can either confirm that it is a bug and even
> > better fix it or let us know what we're missing.
> >
> > Here's the issue. When a user selects a language in which search results
> > are displayed via the language selection button from the Wikipedia main web
> > page, the following JavaScript function is executed:
> >
> > 1 function setLang(lang) {
> > 2 var uiLang = navigator.language || navigator.userLanguage, date
> > = new Date();
> > 3
> > 4 if (uiLang.match(/^\w+/) === lang) {
> > 5 date.setTime(date.getTime() - 1);
> > 6 } else {
> > 7 date.setFullYear(date.getFullYear() + 1);
> > 8 }
> > 9
> > 10 document.cookie = "searchLang=" + lang + ";expires=" +
> > date.toUTCString() + ";domain=" + location.host + ";";
> > 11 }
> >
> > Depending on the evaluation result of the conditional expression on line
> > 4, "uiLang.match(/^\w+/) === lang", the function leaves or dose not leave
> > the selected language information on the user's computer through a cookie.
> > But we found that the expression, "uiLang.match(/^\w+/) === lang", always
> > evaluates to false, which results in that the function always leaves
> > cookies on users' computers. We think that changing the contidional
> > expression, "uiLang.match(/^\w+/) === lang", to the expression,
> > "uiLang.match(/^\w+/) == lang", will solve the problem.
> >
> > This problem may occur in the main web pages of all the Wikimedia sites.
> > Could you kindly let us know what you think? Thank you in advance.
> >
> > Best,
> > Changhee Park and Sukyoung Ryu
> >
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
If you want to write some Swift in the main Wikipedia iOS app project,
please work off the "swift" branch.
Happy hacking!
Brian
--
EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
IRC: bgerstle
Hello!
Tomorrow (Sunday May 24th) at the Lyon Hackathon we will have a
conversion and documentation sprint on extension registration at 17:00
in the Fourvière room.
<https://tools.wmflabs.org/extreg-wos/> has a list of extensions that
have been converted and which still need to be converted! Stop by if you
want to work on converting an extension, learn about the new system, and
find out what's next! I'll also be working on improving the
documentation for sysamdins and developers at that time.
Phab task: https://phabricator.wikimedia.org/T90022
-- Legoktm
[x-post from labs-l to make sure all ssh users receive it]
Hi all,
recently we have been making some changes to global sshd config for
enhanced security.
Since there have been questions and user reports about this on IRC,
let me list them all in detail:
a) optimized symmetric cipher list:
https://gerrit.wikimedia.org/r/#/c/185325/
We prefer the better Chacha20-poly1305,AES-CGM ciphers here now where possible.
This has been merged on 04-27 already and the only problem report we
had was from a user of a really outdated putty version and that could
be solved by upgrading.
b) set Message Authentication Code ciphers
https://gerrit.wikimedia.org/r/#/c/185329/ (see commit message for
more details)
We stop using MD5 or SHA1 because they are insecure and use Encrypt-then-MAC.
This has been merged today and we have had 1 report on IRC so far from
a user who got "no matching MAC found" but apparently was able to fix
it by adjusting the client config.
c) don't use NIST key exchange protocols
https://gerrit.wikimedia.org/r/#/c/185321/ (see commit message for
more details)
This has also been merged today.
We stopped using NIST protocols here because they can't be trusted,
see commit message for details why.
We have had 2 users so far report on IRC getting a "no acceptable hex
algorithm" error. Both were users of MySQL workbench.
There is a related bug at https://bugs.mysql.com/bug.php?id=74658
About the reasoning for these 3 changes in detail, also see:
http://stribika.github.io/2015/01/04/secure-secure-shell.html.
Many quotes on the commit messages are from that source.
d) disable root logins, disable agent forwarding
https://gerrit.wikimedia.org/r/#/c/160628/https://gerrit.wikimedia.org/r/#/c/199936/
These both exist in code review but are _NOT_ merged and are still
being discussed. There is no immediate plan to merge them soon.
Finding the right balance between security and supporting older
clients can sometimes be tough, so sorry for any possible inconvience
caused and let us know if any other issues that can't be solved by
upgrading clients.
Best regards,
Daniel
--
Daniel Zahn <dzahn(a)wikimedia.org>
Operations Engineer
<review>
<rant>
Arcanist has to be manually cloned from Git and added to $PATH. Really?
"Test Plan" is required.
".arcconfig" should be automatically detected on git clone.
I can't review my own revisions.
"Lint" and "Unit" are shown as completely different processes.
Diffs all over the page clutter the UI.
No powerful plain-text Gerrit-like queries.
I have to click "Edit Revision" to add reviewers.
No -2/-1/+1/+2. WTF?
</rant>
<yay>
Tokens!
Comment preview!
Can paste raw diffs!
</yay>
<summary>
Some nice features aren't worth a change of workflow.
</summary>
</review>
> Hi all,
>
> I'm happy to see progress on the node service template project and I'm
> proud that mathoid is one of the earliest adopters.
> I have tested the new mathoid version on
> (http://math-preview.wmflabs.org) with a custom puppet role
> https://gerrit.wikimedia.org/r/#/c/211957/ that is still based on my
> custom debian package.
> For me it's not completly what the strategy for the deployment of the
> node_modules is. Is there an example / guide on how to test the new
> node services on vagrant?
> However, once the new version is deployed, we could enable the new png
> images as default and users would not notice much of a difference.
> However, a change like that would need to be monitored carefully. And
> someone other than me would need to be prepared to fix potential
> problems within a short response time.
>
> Best
> Moritz