Hello!
Just to make this explicit and not hidden in the depth of the
1.27.6/1.30.2/1.31.2/1.32.2 release announcement - MediaWiki 1.27 and 1.30
are
now End-of-Life (EOL) as of Today and are therefore no longer supported.
MediaWiki 1.27 has been slated to become EOL in June 2019 [1], and
therefore the
final release of the MediaWiki 1.27 branch in the form of 1.27.6 solidifies
this.
MediaWiki 1.30 was supposed to be EOL in December 2018 [1], but due to a
lack of
a release since 1.30.1 in September 2018, this hadn't formally happened.
MediaWiki 1.30.2 therefore is the final release for the MediaWiki 1.30
branch.
If you require an LTS version of MediaWiki, please upgrade to MediaWiki 1.31
which is supported until June 2021 [1]. If you don't require LTS support,
you
can upgrade to 1.32 which will be supported till January 2020 [1].
And as somewhat of a heads up, MediaWiki 1.33 is due to be released later
this
month [1].
Thanks!
Sam
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
1.32.2
1.31.2
1.30.2
1.27.6
This will resolve 12 issues in MediaWiki core, and also includes some
previously committed to git minor security and hardening patches.
Fixes will be available in these respective release branches,
and also master. Tarballs will be available for the above mentioned
point releases as well.
1.30 was due to be previously announced as end of life [1], and as
such 1.30.2 will be the final security and maintenance release
barring any unforeseen issues.
1.27.6 will also be the final release for 1.27 (barring any unforeseen
issues), which is scheduled to become end of life in June 2019 [1].
This security release includes fixes for MediaWiki core.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
---
Sam Reed
Hi
We have published a new version of MWoffliner: the MediaWiki scraper.
Version 1.9 is - like always - available here:
https://www.npmjs.com/package/mwoffliner
This new release contains again big improvements in term of performance.
MWoffliner 1.9 does require a lot less memory than in earlier version
thanks to the release of new libzim 5.0.0 which happens a few days ago.
Beside this a new experimental feature as been introduced: the scraping
of categories.
Here is the detailed changelog:
* NEW: Implement basic category scraping (#15)
* UPDATE: Update node-libzim (and libzim) to improve memory usage (#706)
* UPDATE: Increase default scrape "speed" (#744)
* UPDATE: Report on failed article downloads ()
* UPDATE: Retry all failed media downloads at the end of scrape (#723)
* UPDATE: Re-introduce --useCache option (#700)
* UPDATE: Reduce system dependencies (#681)
* UPDATE: Use native <details> element for collapsible sections in ZIM
files (#677)
* FIX: Update article title logic (#605)
* FIX: Logging format improvements (#662)
* FIX: Redis clearing improved (#732, #731, #448)
* FIX: Text only article list main page background colour fixed (#728)
* FIX: Resource relative url improvement (#726)
This is the fourth milestone of a few we have planned with the support
of the WMF.
Like always, PR and bug reports are welcome at:
https://github.com/openzim/mwoffliner
Regards
Emmanuel
--
Kiwix - Wikipedia Offline & more
* Web: http://www.kiwix.org
* Twitter: https://twitter.com/KiwixOffline
* more: http://www.kiwix.org/wiki/Communication
Hi,
I am thinking seriously about creating, or at least helping to oversee the
creation of, a MediaWiki extension that lets users create flowcharts for
use in BPM (business process management, or business process modeling). The
extension would most likely be a wrapper around bpmn-js, an open source
JavaScript library that does this sort of thing pretty nicely:
http://bpmn.io/toolkit/bpmn-js/
There already is a MediaWiki extension that includes bpmn-js - Cognitive
Process Designer:
https://www.mediawiki.org/wiki/Extension:Cognitive_Process_Designer
However, my understanding is that it no longer works with recent versions
of MediaWiki. Also, I disagree with some of the design decisions made on
that extension, so I think creating a new extension makes sense.
I'm not actually looking for funding or development help at the moment -
though both of those would be great to have - but rather some advice. I'm
looking for people who have dealt with BPM, and would like to be able to
edit and display such charts, and BPM information in general, in a wiki. If
this description fits you, please email me back - I have a bunch of
questions and ideas I want to bounce off other people.
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com