Last modified: 2014-09-23 19:53:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47666, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45666 - Deployment review of NamespaceRelations for Wikinews and Wiktionary
Deployment review of NamespaceRelations for Wikinews and Wiktionary
Status: NEW
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 13228 31235
  Show dependency treegraph
 
Reported: 2013-03-03 17:13 UTC by Pavel Selitskas [wizardist]
Modified: 2014-09-23 19:53 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Pavel Selitskas [wizardist] 2013-03-03 17:13:13 UTC
I'm requesting a deployment review for NamespaceRelations[0] extension, which was written for Wikinews[1] and Wiktionary[2]. This piece hasn't been deployed to any wiki yet. Link to Gerrit is listed in [0].

--
[0] https://www.mediawiki.org/wiki/Extension:NamespaceRelations
[1] https://en.wikinews.org/wiki/Wikinews:Water_cooler/technical/archives/2013/January#Opinions_tab:_extension_vs._MediaWiki:Comments.js
[2] https://en.wiktionary.org/wiki/Wiktionary:Grease_pit/2013/January#Citations_tab:_extension_vs._citations_tab.28.29
Comment 1 Andre Klapper 2013-03-05 10:20:20 UTC
Assuming you refer to https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Review_for_deployment and that both Design review and Code review have successfully taken place already.

CC'ing sumanah to find a reviewer.
Comment 2 Pavel Selitskas [wizardist] 2013-03-05 11:23:42 UTC
(In reply to comment #1)
> Assuming you refer to
> https://www.mediawiki.org/wiki/
> Writing_an_extension_for_deployment#Review_for_deployment
> and that both Design review and Code review have successfully taken place
> already.
> 
> CC'ing sumanah to find a reviewer.

Yes, although design review request didn't get much attention[1], code review[2] pointed out some issues which were further resolved.

--
[1] http://lists.wikimedia.org/pipermail/design/2013-January/000296.html
[2] http://lists.wikimedia.org/pipermail/wikitech-l/2013-February/066348.html
Comment 3 Andre Klapper 2013-03-20 14:30:21 UTC
Pavel: Does that mean that everything has been addressed, or is there anything particular still outstanding or blocking?
Comment 4 Pavel Selitskas [wizardist] 2013-03-20 14:44:54 UTC
(In reply to comment #3)
> Pavel: Does that mean that everything has been addressed, or is there
> anything
> particular still outstanding or blocking?

Yes, hooking was simplified and call-time passing by reference deprecations were taken into account and also fixed.

Antoine Musso <hashar> intended to deploy it on a beta cluster about a month and a half ago, but that wasn't done (I'd actually prefer that to be done at the first place, so that people can see what it is and whether it differs, or not, from the current JavaScript implementation).

Addressing your question, I don't observe any blocks out there, although it doesn't mean there aren't any. :)
Comment 5 Antoine "hashar" Musso (WMF) 2013-04-10 08:10:09 UTC
The extension code is already available on the beta cluster since the extension is registered as  submodule of mediawiki/extensions.git

If one would like to enable it, that should be done in the operations/mediawiki-config.git repository.

In wmf-config/InitialiseSettings.php create a global setting to easily enabled/disable the extension:

$wmgUseNamespaceRelations => array(
 'default' => false,
);


Actually use the setting in wmf-config/CommonSettings.php :

if( $wmgUseNamespaceRelations ) {
 include "$IP/extensions/NamespaceRelations/NamespaceRelations.php";
}


Finally enable the setting on labs in wmf-config/InitialiseSettings-labs.php add in the wmfLabsSettings() array:

 '-wmgUseNamespaceRelations' => array(
   'default' => true,
  )

The '-' in front of the name instruct to override whatever settings production might have, since I guess we will always want the extension to be enabled.

Then submit for review, get someone to merge it and it will self deploy via the job https://integration.wikimedia.org/ci/view/Beta/job/beta-mediawiki-config-update/ .
Comment 6 Sam Reed (reedy) 2013-04-22 20:10:04 UTC
Would be beneficial to add some profiling calls, even more so in injectTabs

https://www.mediawiki.org/wiki/Manual:How_to_debug#Advanced_profiling
Comment 7 Greg Grossmeier 2013-06-12 17:42:50 UTC
Pavel: could you see about doing some profiling, as per Reedy's suggestion in comment 6? Thanks.
Comment 8 Pavel Selitskas [wizardist] 2013-06-12 17:49:49 UTC
(In reply to comment #7)
> Pavel: could you see about doing some profiling, as per Reedy's suggestion in
> comment 6? Thanks.

Yes, sorry for such a delay! Would adding wfProfilingIn/Out calls be enough?

Also, after I9fe5728 I'd suggest myself writing some tests to avoid such nasty bugs. That demands further refactoring to make the code testable at some level.

There is one more use case that was not addressed: when we move a page, we suggest that talk page is moved to. Currently, any other pages bonded by means of this extension are not moved. I've already seen the code for moving pages, and it looks kind of ancient, but I'll try working it out. :)
Comment 9 Gerrit Notification Bot 2013-08-14 13:54:12 UTC
Change 79050 had a related patch set uploaded by Wizardist:
(Bug 45666) Add profiling calls

https://gerrit.wikimedia.org/r/79050
Comment 10 Gerrit Notification Bot 2013-08-30 12:13:02 UTC
Change 79050 merged by Wizardist:
(Bug 45666) Add profiling calls

https://gerrit.wikimedia.org/r/79050
Comment 11 This, that and the other (TTO) 2014-01-03 05:59:57 UTC
What is the status here? This would be cool to have on Wiktionary.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links