This past week, we've successfully pushed the preliminary version of 1.17 out to the Wikimedia servers. As anyone familiar with large software deployments could tell you, this uncovered some more bugs that we hadn't yet caught.
We've spent the time taking bug reports and triaging them, figuring out what we need to fix, how important the bug is, etc.
In the hope that someone is looking for a weekend programming project, I'm posting the list of bugs here, sorted by importance and impact.
If you want to fix something that has a lot of impact, it is probably best to start at the top. If you're looking for an easy weekend of hacking, you're probably better off starting close to the bottom.
In any case, we would like to get these bugs need to be fixed before we begin putting a 1.17 tarball together. That's an important milestone for me personally since I want to start working on the 1.18 release sooner rather than later.
If you do decide to start working on one of these, please respond on-list so that we'll have an idea of how much interest there is in this sprint to a release 1.17.
I'm also not done setting priorities, and would love some help with that. (For the purpose of this sprint, ignore the priority settings I talked about in my earlier email.)
If you are pretty sure the priority is wrong, and it doesn't look like anyone else has touched the priority, then be bold and set it (I reserve the right to reset it). If there is something where I've set the priority, but you don't agree, then reply on list or, for faster response, ping me (hexmode) on IRC.
I don't want to encourage edit wars, but I'd like to make sure that the list has a reasonably accurate ordering, so that we don't let really critical problems in this release linger longer than they need to.
And now, without further delay, the bug list:
27528 JS minification still outputs incorrect javascript for some input 27484 File pages created by UploadWizard in Explorer have empty categories 27496 Edit screen autoscrolling 27544 SVG images that are invalid XML no longer rendered 27524 LocalisationUpdate failed
27495 Change NS_USER and NS_USER_TALK namespaces at ptwiki 27467 preload can leave UNIQ 27328 using relative paths in CSS imports in MediaWiki:Common.css broken in 1.17 27540 width of <gallery> always 100% 27486 Special:Import ignoring destination namespace, providing incorrect source in logs
27490 [regression] RTL ui in LTR wiki is LTR aligned 27546 RSS/Atom feed of user contributions broken due to deletedOnly param in link 27489 Update math/texvc module on WMF projects 27547 File search results broken 27506 <gallery> is printed in 1 file per row
27510 In 1.17, template redirects are not shown under the edit box 27302 RL: Avoid unnecessary and uncached requests for user and site modules 27355 Classic edit toolbar buttons fail in IE6 when WikiEditor automatically falls back 27534 proofreadpage JS error. 27470 Upload blacklist for target names not being applied ?
24859 Redirect to mobile gateway should be handled on the server-side rather than the client-side 27499 "Stub size threshold" in preferences doesn't work 27472 Foreign files now have (( )) instead of () 27513 Flagged revs ajax loading of revision + category pages on diffs breaks on image pages. 27352 Wikimedia deployment needs /w/resources directory symlinked or overridden for debug mode
27515 wgVectorModules, wgWikiEditorModules JS variables removed 27432 Set foreground color in vector 27539 some pagelist parameters are no longer passed to the extension 27480 Maintenance script to update page_props
Also can be seen (sorted by bug number) at https://bugzilla.wikimedia.org/showdependencytree.cgi?id=27339&hide_reso...
Other bugs blocking 1.17 release: https://bugzilla.wikimedia.org/showdependencytree.cgi?id=26676&hide_reso...
Mark.
Thanks for all the work, Mark. Few remarks, because it looks to me as if WMF priorities and MediaWiki 1.17 release priorities have been mixed in the list you posted.
WMF issues: * 27495 Change NS_USER and NS_USER_TALK namespaces at ptwiki * 27489 Update math/texvc module on WMF projects * 24859 Redirect to mobile gateway should be handled on the server-side
Also some extension bugs could probably not be seen as blockers for a MediaWiki 1.17 release: * 27484 (UploadWizard is not expected to have huge adaption as long as it's an extension)
Siebrand
Op 19-02-11 06:10 schreef Mark A. Hershberger mhershberger@wikimedia.org:
And now, without further delay, the bug list:
27528 JS minification still outputs incorrect javascript for some input 27484 File pages created by UploadWizard in Explorer have empty categories 27496 Edit screen autoscrolling 27544 SVG images that are invalid XML no longer rendered 27524 LocalisationUpdate failed
27495 Change NS_USER and NS_USER_TALK namespaces at ptwiki 27467 preload can leave UNIQ 27328 using relative paths in CSS imports in MediaWiki:Common.css broken in 1.17 27540 width of <gallery> always 100% 27486 Special:Import ignoring destination namespace, providing incorrect source in logs
27490 [regression] RTL ui in LTR wiki is LTR aligned 27546 RSS/Atom feed of user contributions broken due to deletedOnly param in link 27489 Update math/texvc module on WMF projects 27547 File search results broken 27506 <gallery> is printed in 1 file per row
27510 In 1.17, template redirects are not shown under the edit box 27302 RL: Avoid unnecessary and uncached requests for user and site modules 27355 Classic edit toolbar buttons fail in IE6 when WikiEditor automatically falls back 27534 proofreadpage JS error. 27470 Upload blacklist for target names not being applied ?
24859 Redirect to mobile gateway should be handled on the server-side rather than the client-side 27499 "Stub size threshold" in preferences doesn't work 27472 Foreign files now have (( )) instead of () 27513 Flagged revs ajax loading of revision + category pages on diffs breaks on image pages. 27352 Wikimedia deployment needs /w/resources directory symlinked or overridden for debug mode
27515 wgVectorModules, wgWikiEditorModules JS variables removed 27432 Set foreground color in vector 27539 some pagelist parameters are no longer passed to the extension 27480 Maintenance script to update page_props
Also can be seen (sorted by bug number) at https://bugzilla.wikimedia.org/showdependencytree.cgi?id=27339&hide_reso... ed=1
Other bugs blocking 1.17 release: https://bugzilla.wikimedia.org/showdependencytree.cgi?id=26676&hide_reso... ed=1
Mark.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Siebrand Mazeland s.mazeland@xs4all.nl writes:
Thanks for all the work, Mark. Few remarks, because it looks to me as if WMF priorities and MediaWiki 1.17 release priorities have been mixed in the list you posted.
Good point. The list was based on blockers of Bug #27339, a bug we were using internally to track issues that we knew affected WMF sites. To make this more relevant the the broader MediaWiki community, I'll take some time to add those that are not WMF-specific to the Bug #26676 and the next time I post a list (probably Monday) I'll use that list.
2011/2/19 Mark A. Hershberger mhershberger@wikimedia.org:
27528 JS minification still outputs incorrect javascript for some input
Currently only describes hypothetical problems, one of which even JSMin doesn't solve. The reporter said they had some C code that might be useful, so I asked them to provide it.
27496 Edit screen autoscrolling
I'll investigate this next, after dinner.
27544 SVG images that are invalid XML no longer rendered
TheDJ and Bryan are investigating this and seem to have made some progress.
27524 LocalisationUpdate failed
Almost fixed. LocalisationUpdate runs happily again, but its results aren't getting synced to the cluster just yet because a cron job needs to be updated, and I don't have access to it. I have been poking Mark, will try poking Ryan, but I'm not very optimistic since it's Saturday.
27495 Change NS_USER and NS_USER_TALK namespaces at ptwiki
Hashar fixed this.
27328 using relative paths in CSS imports in MediaWiki:Common.css broken in 1.17
I fixed this in trunk, will deploy later today.
27489 Update math/texvc module on WMF projects
I'll poke at this later.
27302 RL: Avoid unnecessary and uncached requests for user and site modules
Fixed in trunk.
27355 Classic edit toolbar buttons fail in IE6 when WikiEditor automatically falls back 27534 proofreadpage JS error.
Will investigate these two later.
24859 Redirect to mobile gateway should be handled on the server-side rather than the client-side
That's a WMF issue that's difficult to resolve, and it's been an issue long before 1.17 was deployed.
27472 Foreign files now have (( )) instead of ()
Had to do with the LocalisationUpdate problems, was fixed earlier today.
27352 Wikimedia deployment needs /w/resources directory symlinked or overridden for debug mode
I'll look into that.
Roan Kattouw (Catrope)
Roan Kattouw roan.kattouw@gmail.com writes:
24859 Redirect to mobile gateway should be handled on the server-side rather than the client-side
That's a WMF issue that's difficult to resolve, and it's been an issue long before 1.17 was deployed.
I agree it is a WMF issue and, yes, it has been an issue longer than 1.17 has been around, but it seems like the deployment of ResourceLoader has made this a higher priority. I know we've gotten more complaints since RL has gone live.
On 19/02/11 18:20, Roan Kattouw wrote:
27489 Update math/texvc module on WMF projects
I'll poke at this later.
Watch out with this one. I have made some changes in the ocaml math which I have only tested locally.
There is also bug somewhere that ask for the math cache to be refeshed/deleted. IIRC, related to the forced white background made transparent.
On 19/02/11 16:10, Mark A. Hershberger wrote:
In any case, we would like to get these bugs need to be fixed before we begin putting a 1.17 tarball together. That's an important milestone for me personally since I want to start working on the 1.18 release sooner rather than later.
I don't think we're that close to being ready for a tarball release. Before we do a tarball release, we need to have an installer that works, both with fresh installs and upgrades, in all three open source DBMSes and preferably Oracle as well. Last time I checked, it wasn't just buggy, there were major parts missing.
-- Tim Starling
Tim Starling tstarling@wikimedia.org writes:
Before we do a tarball release, we need to have an installer that works, both with fresh installs and upgrades, in all three open source DBMSes and preferably Oracle as well.
I agree that we need them working.
In my testing of MySQL, it seems to work. There is bug #12070 that needs to be addressed, but I don't think that will require a large amount of work.
PostgreSQL had some issues which I tried to address. I've heard reports of problems, but it looks like they've all been addressed. It does need more testing.
I don't know of any problems with SQLite installation that should block release, but that doesn't mean there aren't any.
(I can't test Oracle, so I don't know anything about it. I agree we should have it working, but I don't think it should be a blocker if it isn't working.)
Please look over the bugs against the Installer and, if you see something that should block a 1.17 release, make sure it is is a blocker on bug #26676.
Finally, If there is a blocker issue that you know about but that isn't in Bugzilla, then please report it in Bugzilla and make it a blocker on bug #26676.
Thanks,
Mark.
mhershberger@wikimedia.org (Mark A. Hershberger) writes:
PostgreSQL had some issues which I tried to address.
I owe an apology to Tim for this statement. In my excitement about the sprint I forgot about his comments on Bug #26612 which have not yet been addressed in the PostgreSQL installer.
I'll have a chance to address that on Wednesday, but if anyone else wants to take a shot before then, feel free!
Mark.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
In article 87k4gtb20p.fsf@everybody.org, Mark A. Hershberger mhershberger@wikimedia.org wrote:
(I can't test Oracle, so I don't know anything about it. I agree we should have it working, but I don't think it should be a blocker if it isn't working.)
You might know this already, but you can download Oracle Database from oracle.com, and use it for free for the purpose of application development or testing.
- river.
Hi!
You might know this already, but you can download Oracle Database from oracle.com, and use it for free for the purpose of application development or testing.
I'd think whoever cares already know about that. I don't see why WMF should be directly working on that though ;-)
Domas
On 22/02/11 21:26, Domas Mituzas wrote:
Hi!
You might know this already, but you can download Oracle Database from oracle.com, and use it for free for the purpose of application development or testing.
I'd think whoever cares already know about that. I don't see why WMF should be directly working on that though ;-)
I used it for r81084. Maybe a misuse of WMF time, but I couldn't bear the thought that I had committed untested, broken code.
Downloading it turned out to be more difficult than I thought, since you have to create an account on the Oracle website, and the relevant webserver was down. Bugmenot.com saved the day.
-- Tim Starling
wikitech-l@lists.wikimedia.org