Last modified: 2013-12-15 21:00:29 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 T50095, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 48095 - Tracking: integration with Extension:Nonlinear
Tracking: integration with Extension:Nonlinear
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
master
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 48096 48120 48122
Blocks:
  Show dependency tree / graph
 
Reported: 2013-05-05 05:47 UTC by Adam Wight
Modified: 2013-12-15 21:00 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Adam Wight 2013-05-05 05:47:19 UTC 
jfyi, I'm trying to provide a "nonlinear" plugin for FlaggedRevs which will manage pending changes each on their own branch.  Mentioning it here cos I would like to chat about it.

See also [[mw:Requests_for_comment/Nonlinear_versioning]] for the ten-foot-view of what I'd like to accomplish.
Comment 1 Andre Klapper 2013-05-06 09:15:55 UTC 
So what exact and definable criteria need to happen to mark this bug report as "FIXED"? Feels very vague to me currently. :-/
Comment 2 Adam Wight 2013-05-06 15:04:10 UTC 
I added some dependencies to clarify my proposed implementation.  What needs to happen is that Extension:Nonlinear alters the workflow so that any non-"stable" revisions are created on their own branch, and review acceptance results in a merge process back to trunk.

The whole plan is contingent on acceptance of the "Nonlinear" proposal, obviously.  Without that extension installed, FlaggedRevs will behave exactly as it does currently.
Comment 3 Aaron Schulz 2013-12-15 21:00:29 UTC 
This should be a different extension all together.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links