Hello there,
This message is mostly for the core developper team (the guys that keep flooding cvs with HUGE changes and new features).
As I still havent found any roadmap for the development of mediawiki, I will assume the main page of test.wikipedia.org act as a roadmap.
The new features are: * New skin * Links in thumbnails * Template syntax * Tweaks to localisation * Automatic conflig merging * Greyed subsection in comments * Categories * XML Import * RSS syndication * Hieroglyphs
I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
cheers,
On Thu, Apr 22, 2004 at 04:43:40PM +0200, Ashar Voultoiz wrote:
Hello there,
This message is mostly for the core developper team (the guys that keep flooding cvs with HUGE changes and new features).
As I still havent found any roadmap for the development of mediawiki, I will assume the main page of test.wikipedia.org act as a roadmap.
The new features are:
- New skin
- Links in thumbnails
- Template syntax
- Tweaks to localisation
- Automatic conflig merging
- Greyed subsection in comments
- Categories
- XML Import
- RSS syndication
- Hieroglyphs
I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
My ToDo-list: * Change CSS to use new thumbnail layout (while at it, try to use two CSS files per page, one for common settings, one for skin-specific settings) * Re-add code for processing of non-breakable space for French typography. French uses a space between some punctuation and the next/previous word, that is supposed to be non-breakable. e.g. � Qu'est-ce-que c'est ? � Only the middle space may be used as a line break.
ToDo's I would prefer someone else to do, since I'm not familiar with the code:
* rebuildlinks.php etc don't work when doing a in-place installation. * command line installation doesn't work.
Regards,
JeLuF
On Apr 22, 2004, at 07:43, Ashar Voultoiz wrote:
I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
Fix bugs, bugs, bugs, bugs, bugs, bugs, bugs, and bugs.
Documentation updates.
Additional touches to in-place install. Removal of the old, dangerous command-line install. Getting maintenance scripts usable (but safe) in the in-place environment.
Make sure upgrading from previous versions is a clean, easy process.
Finish cleaning up Preferences.
MonoBook is still missing the occasional bit (for instance, there is no printable-version or RSS link.)
Update all the language files with new stuff.
Finish Special:Import.
-- brion vibber (brion @ pobox.com)
Brion Vibber wrote:
On Apr 22, 2004, at 07:43, Ashar Voultoiz wrote:
I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
Fix bugs, bugs, bugs, bugs, bugs, bugs, bugs, and bugs.
Since when have we ever worried about that? ;)
Documentation updates.
Additional touches to in-place install. Removal of the old, dangerous command-line install. Getting maintenance scripts usable (but safe) in the in-place environment.
I've already checked in a method for checking if a command-line script really is being run from the command line, and exiting with an error message if it isn't. IMHO the best thing to do with the command line scripts would be to convert them to scripts runnable from the ordinary web interface, with password-based (possibly SSL) authentication.
Make sure upgrading from previous versions is a clean, easy process.
I'm worried about the help namespace -- a number of messages have been changed to point to the Help namespace instead of the Wikipedia namespace. This will break links, and may go unnoticed on smaller installations.
Is there any way to execute scripts for schema changes from the web installer? It would be nice to see convertLinks.php work from the web interface. Note that convertLinks.php will require downtime, perhaps an hour or so depending on the speed of the speed of the database server.
moveCustomMessages.php doesn't require downtime, although to safely avoid downtime requires some human know-how. Again, it's only runnable from the command line.
In the long term (post 1.3) it might be nice to have a general way to deal with schema changes, involving automatic detection of missing fields and tables, based on a single schema specification. The specification could then be used for both installing and updating.
Finish cleaning up Preferences.
MonoBook is still missing the occasional bit (for instance, there is no printable-version or RSS link.)
Update all the language files with new stuff.
Gabriel has suggested switching our language management stuff to a utility such as GNU gettext, to make this task easier.
http://www.gnu.org/software/gettext/gettext.html
Needless to say, it would require a lot of work to maintain the current ability to configure via the web interface. Definitely a job for a later release.
There's a few bits and pieces I'd like to get done before 1.3, but I'm not sure if I'll have time. For example, the template parameter syntax chokes on something like {{thing|x=[[Foo|Bar]]}}. I think the solution is to move the brace handling code to the tokenizer section.
The other thing that I want to do is to work on profiling and optimisation. The main entry point of the parser is called a lot more often than it used to be, I think there might be some need for moving various kinds of initialisation to the constructor, or to static variables.
We're getting pretty tight for CPU time at the moment, it seems to be causing minor slowdowns in peak times. It might be wise to fix up Snok's parser cache and enable it on the live site.
-- Tim Starling
The roadmap can be found at the following address: http://meta.wikipedia.org/wiki/MediaWiki_roadmap
For my part, WikiHiero is already operational and stable, but I still have many features I'd like to add: - A full CSS version (convert XHTML depreciated tag/arguments in styles) - More syntax's support (comment, annotation, bracket, number converter, etc.) I will continue to submit changes until the start of the beta test phase, stabilize the version until the release, and then continue to submit changes to the next version.
Aoineko
----- Original Message ----- From: "Ashar Voultoiz" thoane@altern.org To: wikitech-l@wikipedia.org Sent: Thursday, April 22, 2004 11:43 PM Subject: [Wikitech-l] Getting to MediaWiki 1.3
Hello there,
This message is mostly for the core developper team (the guys that keep flooding cvs with HUGE changes and new features).
As I still havent found any roadmap for the development of mediawiki, I will assume the main page of test.wikipedia.org act as a roadmap.
The new features are:
- New skin
- Links in thumbnails
- Template syntax
- Tweaks to localisation
- Automatic conflig merging
- Greyed subsection in comments
- Categories
- XML Import
- RSS syndication
- Hieroglyphs
I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
cheers,
-- Ashar Voultoiz http://fr.wikipedia.org/Utilisateur:Hashar
Wikitech-l mailing list Wikitech-l@Wikipedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
On Thu, Apr 22, 2004 at 04:43:40PM +0200, Ashar Voultoiz wrote:
Hello there,
This message is mostly for the core developper team (the guys that keep flooding cvs with HUGE changes and new features). [...] I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
I took all the todos mentioned in the mails and summarized them at http://meta.wikipedia.org/wiki/MediaWiki_roadmap#To_be_done
Feel free to update these if points are resolved.
Regards,
jens
On Fri, 23 Apr 2004 14:41:03 +0200, Jens Frank wrote:
On Thu, Apr 22, 2004 at 04:43:40PM +0200, Ashar Voultoiz wrote:
Hello there,
This message is mostly for the core developper team (the guys that keep flooding cvs with HUGE changes and new features). [...] I am wondering if all of those are ready to make a 1.3 "stable" release or if there is still some work to be done.
If everything is fine, what are we waiting for to release 1.3.0 ? If not wich part should I look at and help finish ? ;)
I took all the todos mentioned in the mails and summarized them at http://meta.wikipedia.org/wiki/MediaWiki_roadmap#To_be_done
Feel free to update these if points are resolved.
Regards,
jens
Thanks to Aoineko for giving the link, thanks to jens for updating it :0)
wikitech-l@lists.wikimedia.org