Page MenuHomePhabricator

Create #beta-cluster-reproducible tag and rename #beta-cluster to #beta-cluster-infrastructure
Closed, ResolvedPublic

Description

The problem
We routinely have tasks reported, and included in the #Beta-Cluster project, that are software defects found when testing on Beta Cluster. The fact that we found those issues on Beta Cluster is AWESOME and GREAT. But they aren't issues with Beta Cluster the service and muddy up the workboard (and any future potential reporting).

Solution

  1. Rename #Beta-Cluster to #beta-cluster-infrastructure
    • Add #beta-cluster as an additional hashtag
  2. Create #Beta-Cluster-reproducible tag
    • Description: "This project tracks issues that were identified on, or are reproducible in, the Beta Cluster testing environment.
    • Type: Tag (yellow+tag icon)
    • Default policy.
  3. Make a column named "On wiki change" (or "Wiki Admin") in #beta-cluster-infrastructure workboard
  4. Move the following open tasks to #Beta-Cluster-reproducible:

Event Timeline

greg raised the priority of this task from to Needs Triage.
greg updated the task description. (Show Details)
greg moved this task to To Triage on the Beta-Cluster-Infrastructure board.
greg added subscribers: greg, Legoktm, hashar and 2 others.

I like the idea of decoupling issues related to the beta cluster itself from the dev/software running on top of it. The first are addressed by ops/releng, the later by devs usually.

Maybe #beta-cluster-reproducable / and rename Beta-Cluster-Infrastructure to #beta-cluster-infrastructure ?

We did a similar split for CI with:

Love the idea, can be done right now and we can always adjust the names later on.

Maybe it could be also a good idea to create a seperate workcolumn for bugs, which you can resolve by change onwiki (like right changes, sysmessage change), per webinterface, for example something like T113660. I can resolve bugs like this fast, and you can focus your work at code issues etc, because this is the thing, that I can't at the moment ;-), but it would be better to resolve onwiki issues faster, because I'm mostly every day at beta, so I can resolve them fast.

Good idea @Luke081515. That could definitely be a column in the Beta-Cluster-Infrastructure or whatever project.

I'm going to let this sit for today, let others see it/comment if they want, and then if there's still consensus early next week (Mon or Tues) I'll make the changes (or someone else can beat me to it).

For the record, my plan for the changes based on this discussion:

  1. Rename Beta-Cluster-Infrastructure to Beta-Cluster-Infrastructure
  2. Create Beta-Cluster-reproducible
    • Description: "This project tracks issues that were identified on, or are reproducible in, the Beta Cluster testing environment.
    • Type: Tag (yellow+tag icon)
    • Default policy.
    • cc @Aklapper: this is me proposing this tag, with plans to create it on Mon or Tuesday ;)
  3. Make a column named "On wiki change" in Beta-Cluster-Infrastructure workboard
  4. Move the following open tasks to Beta-Cluster-reproducible:
greg renamed this task from Identify / separate out software issues found *on* Beta Cluster versus issues with Beta Cluster itself to Create #beta-cluster-reproducible tag and rename #beta-cluster to #beta-cluster-infrastructure.Oct 4 2015, 3:02 AM
greg triaged this task as Medium priority.
greg updated the task description. (Show Details)
greg removed a project: Beta-Cluster-Infrastructure.

@Luke081515 has an excellent idea!

For greg-g plan

antoine-approve

ok, enough +1s, I'll JFDI now.

Everything done except moving those two tasks into -reproducible (it's created) because @Jdforrester-WMF has thoughts on names, and I'll wait to move them until after we rename it, if we do.

(ok, I moved 'em, we can rename the tag later if needed)

Sounds good, @greg would you mind announcing it? Perhaps on QA list, the private engineering list and maybe wikitech-l?

greg updated the task description. (Show Details)

Sounds good, @greg would you mind announcing it? Perhaps on QA list, the private engineering list and maybe wikitech-l?

{{done}}