Page MenuHomePhabricator

Make MediaWiki-Vagrant a Bugzilla product on its own
Closed, ResolvedPublic


As a side-effect of bug 53986 (confusion regarding stuff in Bugzilla that's somehow called "Tools") it was considered to move MediaWiki-Vagrant out of the "Tools" product and making it a product on its own (with potential subcomponents). MediaWiki-Vagrant by far has the highest number of tickets and highest development activity among the components currently under "Tools".

After Ori (MW-Vagrant maintainer) has given his OK here, I am going to

  • create a new product (calling it "MediaWiki-Vagrant" will make differentiating from "MediaWiki" tickets hard in buglist.cgi. On the other hand the issue already exists with "MediaWiki" vs "MediaWiki extensions" so I should just fscking fix bug 40244, finally.)
  • create new initial component "General" and set Ori as default assignee.

> If other components are wanted, tell me.

  • move all 55 tickets from "Tools/MediaWiki-Vagrant" to "MediaWiki-Vagrant/General".
  • remove the component "MediaWiki-Vagrant" from "Tools" product.

For the records, general info on creation of components and products in Wikimedia Bugzilla:

Version: wmf-deployment
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:09 AM
bzimport set Reference to bz54041.

Change 83955 had a related patch set uploaded by Ori.livneh:
Update Bugzilla URLs to reflect change in taxonomy

Change 83955 merged by jenkins-bot:
Update Bugzilla URLs to reflect change in taxonomy

(In reply to comment #2)


Links to Bugzilla that need updating and that I am aware of:



Thanks again!