Last modified: 2014-07-16 21:54:13 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 T61635, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59635 - Splitting the list of protect and stabilization reasons
Splitting the list of protect and stabilization reasons
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-04 03:49 UTC by MaxBioHazard
Modified: 2014-07-16 21:54 UTC (History)
4 users (show)

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


Attachments

Description MaxBioHazard 2014-01-04 03:49:27 UTC
Please divide the list of protection reasons (MediaWiki:Protect-dropdown) into two: for protection and for stabilization. The reasons are as follows: 1) There are different available reasons for protection and for stabilization in the regulations of Wikipedias (including RuWiki). 2) When stabilizing, a sysop sees a group of "Move" reasons. But unlike the move protection, the move stabilization is not technically feasible.
Comment 1 db [inactive,noenotif] 2014-01-04 12:24:51 UTC
stabilization is part of the FlaggedRevs extension -> moving
Comment 2 Gerrit Notification Bot 2014-07-14 23:44:24 UTC
Change 146347 had a related patch set uploaded by Victor Vasiliev:
Introduce a seperate message for stabilization reasons

https://gerrit.wikimedia.org/r/146347
Comment 3 Gerrit Notification Bot 2014-07-16 20:58:19 UTC
Change 146347 merged by jenkins-bot:
Introduce a seperate message for stabilization reasons

https://gerrit.wikimedia.org/r/146347

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


Navigation
Links