---------- Forwarded message ----------
From: "Mark A. Hershberger" <mah(a)everybody.org>
Date: Feb 25, 2013 10:03 AM
Subject: [Wikitech-l] Release policy
To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Cc:
> After the discussion last week, I want to scope out a release policy so
> that we'll all know what to expect.
>
> * A major release will be made every six months.
>
> * An LTS release will be made every two years. There will be a one-year
> overlap in LTS support. For example, 1.19 is supported until May 2015.
> 1.23 will be released the year before that so that people will have 1.23
> available as an LTS to move to and a year to make the transition.
>
> * Releases notes will continue to be the basis for seeing what has
> changed. Because of the nature of a volunteer-driven project, it isn't
> possible to say with any certainty what *will* happen in the next 6-12
> months.
>
> * To mitigate the problem of release notes, we will publish a list of
> new features in the upcoming LTS relative to the last LTS six months
> before it comes out. This means that about the time when 1.22 comes
> out, we'll have an announcement for 1.19 users letting them know what
> changes they can expect in 1.23.
>
> * Point releases will be made periodically. Frequency TBD. Every point
> release will include updated i18n files as well as any bug fixes. No
> new features will be back-ported to point releases.
>
> Thanks,
>
> Mark.
>
> --
> http://hexmode.com/
>
> There is no path to peace. Peace is the path.
> -- Mahatma Gandhi, "Non-Violence in Peace and War"
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
(Adding a couple of mailing lists so others can weigh in. Changing
subject so those added aren't completely lost.)
On 02/21/2013 11:55 AM, Quim Gil wrote:
> Ok, just a question as humble 3rd party MediaWiki user and technical
> volunteer coordinator at the WMF: is there a possibility to consider
> having a regular free software release process?
>
> master/unstable ---> (testing releases?) ---> stable releases
...
> I think the current process is ok-ish in the short term: non-WMF
> contributors are getting +2 and 3rd parties are getting tarballs.
As you say, I think the current process is Ok(ish) for now. We need to
get others in the MediaWiki "ecosystem" involved in core before this
becomes something we really need to do.
It would be great to have developers from other significant MediaWiki
sites (like Referata, Wikia, Citizendium, etc) become more involved and
start introducing features or hooks that they use into core or making
the extensions available. Of course, some of those developers have
already been involved.
But right now, I don't sense a huge amount of friction between the WMF's
needs and the non-WMF MediaWiki-using community. The most that can be
said is that the WMF is focused on its sites and doesn't make third
party use a priority. This doesn't stop support for other databases,
though: Oracle, MS SQL, PostgreSQL, SQLite, or even my recent changes to
separate out DB schema changes in MySQL.
That said, I'm very interested in this conversation. As MZ will remind
you, I did advocate for the formation of the MediaWiki Foundation.
Mark.
--
http://hexmode.com/
There is no path to peace. Peace is the path.
-- Mahatma Gandhi, "Non-Violence in Peace and War"
Axel Thimm and Fedora Release Engineering,
I'm looking for the person in charge of packaging MediaWiki for Fedora.
From the recent changelog, it looks like Axel is that person.
I'd like to start working with you to get the MediaWiki 1.19 series
packaged for Fedora and use that as a basis for working with other
RPM-based distributions.
Even though MW 1.20 is about to be released, I'd like to use 1.19 so
that we can make it an LTS release and collaborate on supporting it.
We (a group of MediaWiki developers, especially Platonides) have been
working with the Debian developers to get 1.19 into Wheezy and have been
able to help them resolve some issues more quickly because of our
familiarity with MediaWiki.
I hope that you'll see the mutual benefit that could come from
collaborating on MediaWiki packaging.
What do we need to do to get the process started?
--
http://hexmode.com/
Any time you have "one overriding idea", and push your idea as a
superior ideology, you're going to be wrong. ... The fact is,
reality is complicated -- Linus Torvalds <http://hexm.de/mc>
Dear all!
Sorry, I didn't have much time to work on packaging in the last weeks; so I'm a little bit un-informed at the moment.
I'd like to tell you what I have developed for the OpenSUSE mediawiki packages in the last years. You can find the resources in
* https://build.opensuse.org/package/show?package=mediawiki&project=server%3A…
* https://build.opensuse.org/package/show?package=mediawiki-math&project=serv…
* https://build.opensuse.org/package/show?package=texvc&project=server%3Aphp%…
1) I have split off the texvc project to a seperated, arch-dependend project
2) The whole installation of mediawiki is LSB compliant. The installation's base is in /usr/share/mediawiki.
To add new instances of mediawiki, there is the script "makealias.sh" which creates a default installation in
/var/lib/mediawiki
+ cache
+ session
+ tmp
+ upload
+ webroot
during RPM creation. The script can also be called manually (it's located in /usr/share/mediawiki/admintools) to create instances of that kind in different locations.
An Apache configuration is created on the fly, each instance is added in /etc/mediawiki-installations
3) The script /usr/share/mediawiki/admintools/update.sh is executed after each update and corrects symlinks and updates the different mediawiki instances.
####
All that files including a readme file can be found on the first location above. There is also the current spec file which does e.g. some file deletions as already mentioned in the mailing-list.
It would be great to co-operate with you to create nice packages for all opensource systems...
--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna
Just quick note that, as announced in August
<http://lists.wikimedia.org/pipermail/mediawiki-l/2012-August/039678.html>,
translatewiki.net yesterday dropped support for about 260
extensions/message groups.
People still using code from SVN will no longer have the localisation
updates they might expect.
If you need or care about one of them and the respective localisation,
you should get in contact with its developer(s) (or become one) so that
it's migrated to
Git.<https://www.mediawiki.org/wiki/Git/Conversion/Extensions_queue>
Most or all of them need some tender loving care anyway.
The list of removed message groups is in
https://gerrit.wikimedia.org/r/#/c/26045/ and reproduced below for your
convenience.
Sorry for the crossposting,
Nemo
ABC, Advanced Meta, Advanced Random, Ajax Login, AJAX Poll, Ajax Query
Pages, Ajax Show Editors, Amazon Plus, Api Explorer, Api SVG Proxy,
Article Comments, Article To Category 2, Asksql, Autoincrement, Back and
Forth, Bad Image, Batch User Rights, Block Titles, Book Information,
CallCassandra, Categorize, Category Browser, Category Intersection,
Category Members On Sidebar, Category Multisort, Category Multisort
Chinese, Category On Upload, Category Sort Headers, Category Stepper,
Category Watch, Change Author, Chemistry, Close Wikis, Collab Watchlist,
Comment Spammer, Contributions Edit Count, Contributors, Contributors
Add-on, Cooperation Statistics, Count Edits, Create Box, Create
Redirect, Creative Commons Rdf, Cross Namespace Links, Crosswiki Block,
Crowd Authentication, Data Transclusion, Date Diff, Delayed Definition,
Delete Queue, Did You Mean, DPL Forum, Dublin Core Rdf, Duplicator, Edit
count, Edit Messages, Edit Own, Edit Section Clearer Link, Edit Section
Hilite Link, Edit Similar, Edit User, Elm Easy Ref, Email Address Image,
Email Page, Email Users, Emergency DeSysop, Etherpad Lite, External
Pages, Farmer, Favorites, File Attach, File Page Masking, Find Spam,
Fixed Image, Flag Page, Flv Handler, Folk Tag Cloud, Form, Format Email,
Framed Video, Freq Pattern Tag Cloud, Front Back Matter Forced
Wikilinks, GeeQuBox, GeoLite, Get Family, Global User rights, Gnuplot,
Google Analytics, Google Maps, Go To Category, Groups Sidebar, Hide
Namespace, Honeypot Integration, HTMLets, Icon, Image Tagging, Import
Free Images, Import Users, IM Status, Include WP, Index Function, Inline
Categorizer, Inspect Cache, Interactive Block Message, Interface
Concurrency, Interwiki List, IP Auth, JS Kit, Last User Login, Latex
Doc, Link OpenID, Livelets, Local JQuery, Lockdown, Logo Functions,
Lookup User, Lua, Magic No Numbered Headings, Mass Blank, Mass Edit
Regex, Math Stat Functions, Media Functions, Metadata Edit, Meta
Keywords, Metavid Wiki, MicroID, Mini Donation, Minimum Name Length,
Mini Preview, Mirror Tools, Most Revisors, Multi Boilerplate, Multi
Upload, Natural Language List, Navigation Popups, Network Auth, Newest
Pages, News, News Channel, No Bogus Userpages, Notificator, Nss MySQL
Auth, OpenID, Oracle Text Search, Other Sites, Package Force, Page By,
Page In Cat, Page Object Model, Parser Wiki, Patroller, Pdf Book, People
Categories, Pipe Escape, Piwik, Player, Plotters, POV Watch, Preloader,
Preview Functions, Private Page Protection, Profile Monitor, Protect
Section, Proxy Connect, PSI NoTocNum, Pure Wiki Deletion, Purge, Purge
Cache, QPoll, Qr Code, Random Image, RDFIO, Record Admin, Redirect,
Reflect, Regex Block, Research Tools, Resumable Upload, RPED, Search
Box, See also, Semantic Data Types, Semantic Project Management,
SemanticSignup, Semantic Web Browser, Sendmail To Wiki, Shared User
Rights, Show Processlist, Sidebar Donate Box, Sign Document, Simple
Security, Slippy Map, SNMP query, Sound Manager 2 Button, Spam Diff
Tool, Spam Regex, Special 404, Special File List, Special Talk,
SQL2Wiki, Stale Pages, Sternograph, Stock Charts, Storyboard, String
Functions, Sudo, Suhosin, SVG Zoom, Tab0, Talk Here, Tasks, Template
Info, Template Link, TidyTab, Todo, Todo Tasks, Toolserver Tools -
Holeks Cite book template generator, Toolserver Tools - Kolossos Kml On
Openlayers, Toolserver Tools - Soxred93, Tooltip, Transliterator, Tree
And Menu, Trusted Math, TSPoll, UK Geocoding For Maps, Uniwiki -
Authors, Uniwiki - Auto Create Category Pages, Uniwiki - Cat Box At Top,
Uniwiki - Create Page, Uniwiki - Css Hooks, Uniwiki - Custom Toolbar,
Uniwiki - Format Changes, Uniwiki - Format Search, Uniwiki - Generic
Edit Page, Uniwiki - Javascript, Uniwiki - Layouts, Uniwiki - Moo Tools
12 core, Usage Statistics, User Contact Links, User Debug Info, User
Images, User Page Edit Protection, User Rights Notif, VariVote,
Watchers, Watch Subpages, Web Store, What Is My IP, White List Edit, Who
Is Watching, Whos Online, Wiki Article Feeds, Wiki At Home, WikiBhasha,
Wikidata, Wikilog, Wiki Sync, Wiki Tweet, Woopra, XMLRC, YouTube Auth Sub.
In order to create the list on Gmane, I'm forwarding this message.
-------- Original Message --------
Subject: mediawiki-distributors added to Gmane
Date: Sat, 29 Sep 2012 11:15:08 +0200
Organization: Mail To News -- http://gmane.org/
To: mediawiki-distributors-admin(a)lists.wikimedia.org,
mediawiki-distributors-admin(a)lists.wikimedia.org
We have received a request for adding the
mediawiki-distributors(a)lists.wikimedia.org mailing list to the Gmane
mail-to-news gateway/archive. A subscription request message has been
sent. If this is contrary to your wishes, please send a mail to
admin(a)gmane.org saying so, and the list will be removed from Gmane.
Gmane is a mail-to-news portal that never expires its messages. It
therefore also functions as a mailing list archive. It's a
bi-directional gateway, but Gmane verifies that its users' email
addresses are valid before passing the messages through the
news-to-mail gateway. (Groups can also be made "read-only", which
means that Gmane won't forward any messages at all to the mailing
list.)
Gmane can encrypt addresses to make address harvesting difficult, and
heeds X-No-Archive and related headers.
If you wish to import older archives into Gmane, send a message to
the Gmane administrators with the URL of a Unix mbox archive of the
mailing list.
In partnership with The Mail Archive, messages will be archived on
that service as well. This provides redundancy across two archival
services.
The following parameters are set for this mailing list:
* Newsgroup name: gmane.org.wikimedia.mediawiki.distributors
* Mailing list address: mediawiki-distributors(a)lists.wikimedia.org
* The gateway is bi-directional
* Address encryption is off
* Spam detection is on
* The list is described as:
"Discussion problems you come across packaging MediaWiki"
* News URL:
news://news.gmane.org/gmane.org.wikimedia.mediawiki.distributors
* Web URL:
http://dir.gmane.org/gmane.org.wikimedia.mediawiki.distributors
This newsgroup will be created when the first message from the
mailing list arrives.
For more information about the Gmane project, go to
<URL: http://gmane.org/>.
For more information about The Mail Archive, go to
<URL: http://www.mail-archive.com/>.
This request was handled by
asjo(a)koldfront.dk (Adam Sjøgren).
Hi,
-------- Original Message --------
> When I migrated from squeeze to wheezy, my mediawiki wiki stopped
> showing content and started showing blank pages. Turning on the
> appropriate setting to print the error messages, I got the
> following message:
>
> Fatal error: Call to undefined method Xml::hidden() in
> /usr/share/mediawiki-extensions/base/LanguageSelector/LanguageSelector.php
> on line 356
Is it appropriate to apply [0] to this case? I'm reluctant to blindly
follow instructions from an unknown (to me) contributor; on the other
hand this is a grave bug as far as Wheezy is concerned and we need to
get it resolved urgently.
Thanks,
--
Jonathan Wiltshire jmw(a)debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
FYI
---------- Forwarded message ----------
From: "Benny Baumann" <BenBE(a)geshi.org>
Date: Aug 19, 2012 3:21 PM
Subject: [Pkg-mediawiki-devel] Bug#685326: Anchient version in stable and
testing although update to more recent version requested for ages.
To: "Debian Bug Tracking System" <submit(a)bugs.debian.org>
Package: php-geshi
Version: 1.0.8.4-1
Severity: serious
Tags: upstream
Despite being asked for about two years ago this package hasn't been updated
by the responsible maintainers. Also direct contact to the maintainers at
several
points in time and occasions achieved no response which would lead to new
and fixed versions of the upstream package resolving all bugs of this
Debian package being updated.
Also in the latest upstream release there are fixes for two security bugs
(reported
to the security team) that need being deployed ASAP a the Debian package
includes
the vulnerable files.
Even though just fixing those two security bugs might seem enough it
actually isn't.
Due to the wide range of web applications that include GeSHi or contain a
plugin to
use GeSHi fixing the three below bugs causes a lot of applications to
profit from
including a new upstream version. This not only fixes a few bugs reported
to Debian
directly but (maybe read the CHANGELOG) quite a lot of different
highlighting problems
people have reported upstream over the last two years.
Thus it'd be /really/ nice if a updated version using latest upstream
1.0.8.11 by the
time of this bug report) could be sent to stable/testing ASAP.
Best regards,
upstream.
Bugs with severity normal
1) #579080 php-geshi: Can't render Scheme code
2) #613711 php-geshi: Incorrect HTML generation while parsing Java
source files
Bugs with severity wishlist
3) #584251 php-geshi: Upstream release 1.0.8.8
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages php-geshi depends on:
ii php5 5.4.4-4
ii php5-cli 5.4.4-4
php-geshi recommends no packages.
php-geshi suggests no packages.
-- no debconf information
_______________________________________________
Pkg-mediawiki-devel mailing list
Pkg-mediawiki-devel(a)lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mediawiki-devel
Stephen (and anyone else who may know),
I told Platonides that I would look at the RPM package for MediaWiki
this weekend, but I can't seem to find what you guys have been
developing. Should I just look at the 1.16 package?
Platonides has been working with the Debian developers on improving
their MediaWiki package and I said I would look at the RPM. We would
really like these the have some sort of feature parity.
Thanks,
Mark.