Further cleanup of #Deployment-Systems
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	greg
	Feb 11 2016, 5:41 PM

Description

In T126261 I created Scap and Trebuchet and moved a bunch of tasks from Deployments to them.

Now I'm looking at Deployments and it looks like we're left with these categories of tasks:

tasks regarding the scripts in mediawiki/tools/release (aka: rMREL MediaWiki Release Tools)
tasks about l10n (which only lives in rOPUP in the scap module)
general process changes (not necessarily code changes) like T118212: Take heat off day before the weekly branch-cut?
"technical things related to deployments generally" eg: T106732, T45086, T45722, etc

This can be 'cleaned up' via a couple options:

Use columns in Deployments to categorize them
Create a few more projects.
...

Working proposal
After discussion on this task here's the current working plan (not yet set in stone):

Rename Deployments to Deployments
- This can hold "technical things related to deployments generally" eg:
- And also meta-process related things eg:
Move Scap, Trebuchet, etc to sub-projects of Deployments
- there is a script for this that Luke wrote? Or at least a how-to, right?
- make a MediaWiki-Release-Tools as a subproject of Deployments
- For tasks regarding the scripts in mediawiki/tools/release (aka: rMREL MediaWiki Release Tools)
Still an open question regarding I18n, l10nupdate (in rOPUP), and MediaWiki-extensions-LocalisationUpdate
- For now I've made a "Localization" column on the Deployments workboard

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		greg	T138884 Redo some #RelEng -related project workboard columns
		Resolved		greg	T126631 Further cleanup of #Deployment-Systems

Event Timeline

greg created this task.Feb 11 2016, 5:41 PM

greg raised the priority of this task from to Needs Triage.

greg updated the task description. (Show Details)

greg added a project: Project-Admins.

greg subscribed.

Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald TranscriptFeb 11 2016, 5:41 PM

Luke081515 triaged this task as Medium priority.Feb 12 2016, 7:33 PM

Luke081515 subscribed.

Danny_B moved this task from Incoming to Needs discussion on the Project-Admins board.Feb 15 2016, 7:29 AM

We could use actual sub-projects now

Not a bad idea.....

tasks regarding the scripts in mediawiki/tools/release (aka: rMREL MediaWiki Release Tools)

Deployments
- mediawiki-release-tools

tasks about l10n (which only lives in rOPUP in the scap module)

l10n
- there may be 2 tags here, localization cache in general and l10nupdate specifically.)

general process changes (not necessarily code changes) like T118212: Take heat off day before the weekly branch-cut?

#deployment-process

"technical things related to deployments generally"

these stay in Deployments

Or, we rename deployment-systems to Deployments and move software related things into specific sub-projects like Scap, #l10n, etc....

I like your last proposal.

In T126631#2058296, @mmodell wrote:

Or, we rename deployment-systems to Deployments and move software related things into specific sub-projects like Scap, #l10n, etc....

I like this, as I said, the only concern I still have is what to call the 'catch-all' sub-project (my understanding, correct me if I'm wrong, is that once you have sub-projects, no tasks can exist in only the parent project). Deployments -> ???

greg added a project: User-greg.Mar 4 2016, 10:06 PM

greg moved this task from Backlog to Next on the User-greg board.

greg lowered the priority of this task from Medium to Low.Mar 22 2016, 8:45 PM

greg set Security to None.

In T126631#2072898, @greg wrote:

In T126631#2058296, @mmodell wrote:

Or, we rename deployment-systems to Deployments and move software related things into specific sub-projects like Scap, #l10n, etc....

I like this, as I said, the only concern I still have is what to call the 'catch-all' sub-project (my understanding, correct me if I'm wrong, is that once you have sub-projects, no tasks can exist in only the parent project). Deployments -> ???

This was a misunderstanding on my part. Tasks can remain in the top-level project even with sub-projects and milestones.

So, summary of plan (as I understand it):

rename Deployments to Deployments
make Scap, Trebuchet, etc a sub-project of Deployments
- there is a script for this that Luke wrote? Or at least a how-to, right?
TODO: Figure out what to do with Scap and Scap
- merge back Scap into Scap but keep the milestones?
  - where "merge" == "make sure all the Scap tasks are in Scap"
  - Scap was intended, initially, as a sprint for the release of scap3, which is now completed...
  - this would require a lot of clean up of the tasks in Scap, which is A Good Thing(TM) (probably)
- convert Scap into a component (from a "sprint") to live alongside Scap (I don't like this one at all)
make a #deployment-process subproject of Deployments
make a MediaWiki-Release-Tools as a subproject of Deployments
Still an open question regarding I18n and MediaWiki-extensions-LocalisationUpdate

Does that make sense? Help with scap/scap3 questions, please!

In T126631#2158425, @greg wrote:

Does that make sense? Help with scap/scap3 questions, please!

pinging @mmodell @thcipriani @demon @dduvall :)

greg moved this task from Next to Needs Review / Blocked / Waiting on the User-greg board.Apr 1 2016, 11:10 PM

(I updated the description with the current working theory as I had in my head.)

In T126631#2158425, @greg wrote:

Does that make sense? Help with scap/scap3 questions, please!

Merging Scap and Scap seems like a good thing to do. It's currently a confusing split. This work would require some triage, but, as you said, that's probably a good thing.

The logistics of this worry me a bit, since the Scap workboard contains a couple milestones: Scap (Scap3-Adoption-Phase1)
Scap (Scap3-MediaWiki-MVP) and #scap3-adoption-phase2. Also, If it matters, the state of the Scap workboard is currently much cleaner than the existing Scap workboard (which currently only contains the column "Backlog"). Ideally, we could just move all the tasks exclusive to Scap into the Scap project and repurpose Scap. Not sure how that would be achieved.

Luckily there's only 41 tasks in scap that aren't in any scap3 project:
https://phabricator.wikimedia.org/maniphest/query/6sRUmqnn8ado/#R

/me looks to see if any are easily closable

greg updated the task description. (Show Details)Apr 8 2016, 10:34 PM

Luke081515 moved this task from Needs discussion to Administration on the Project-Admins board.May 3 2016, 9:35 PM

Danny_B moved this task from Administration to Projects to change / set on the Project-Admins board.May 3 2016, 9:40 PM

greg moved this task from Needs Review / Blocked / Waiting to Next on the User-greg board.May 27 2016, 7:20 PM

greg moved this task from Next to Backlog on the User-greg board.Jun 11 2016, 6:49 AM

greg moved this task from Backlog to Needs Review / Blocked / Waiting on the User-greg board.

greg mentioned this in T138884: Redo some #RelEng -related project workboard columns.Jun 28 2016, 10:13 PM

greg added a parent task: T138884: Redo some #RelEng -related project workboard columns.

greg updated the task description. (Show Details)Sep 26 2017, 10:42 PM

greg updated the task description. (Show Details)Sep 26 2017, 10:46 PM

• Phabricator_maintenance moved this task from To Triage to Backlog (Process) on the Deployments board.Sep 26 2017, 11:22 PM

greg updated the task description. (Show Details)Sep 26 2017, 11:30 PM

Just did a few things:

renamed Deployment-Systems to Deployments
Made a MediaWiki-Release-Tools sub-project, moved a bunch of tasks to it
Cleaned up the Deployments workboard.
- To Triage, Backlog (Tech), Backlog (Process), Localization
Cleaned up the To Triage column down to one, that will probably be closed :)

Things left to do: