Last modified: 2011-03-13 18:05:02 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8048 - Revision levels
Revision levels
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-27 05:16 UTC by Stephanie Daugherty
Modified: 2011-03-13 18:05 UTC (History)
1 user (show)

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


Attachments

Description Stephanie Daugherty 2006-11-27 05:16:04 UTC
As an aid to quality control, I propose a system of revision levels, which can
be selected when editing a revision, and changed from the revision history.

The available revision levels would be defined in the site configuration, along
with a numeric ranking that defines that level's precedence over other levels.

The revision level would control which version of the article gets displayed to
users, and the levels would be ranked such that the highest revision level would
be displayed rather than the highest revision id. 

Default levels should be shipped for published and draft versions, such that
published versions are preferred over draft versions.

With appropriate permissions, this could also offer an viable alternative form
of page protection which would still allow continued contributions to an article
under protection, while discouraging vandalism.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-11-28 03:19:23 UTC
Seems to be basically a generalization of stable versions (bug 3303).  Is the
generalization (more than two "revision levels" possible) useful, considering
the interface ramifications of allowing unlimited levels?  Things like having
one tab for stable and one for unstable, or having a single button to mark a
version stable/unstable, are complicated considerably by the possibility of an
arbitrary number of possibilities to choose from, and I don't know if I see the
point.
Comment 2 Aaron Schulz 2008-01-13 18:59:43 UTC
Much of this is done in FlaggedRevs, the extra complexity is unlikely to be implemented anywhere though.

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


Navigation
Links