Page MenuHomePhabricator

Create Language October–December 2016 and CX11 Phabricator boards
Closed, ResolvedPublic

Description

The following boards will be needed soon:

  • Language October–December 2016
  • Language October–December 2016 sprints
  • CX11 release

In the past I was often late with pre-filling the boards with the proper columns and tasks when the quarter already started (totally my bad), so I'm creating the tasks already now to make sure that the boards are created as early as possible.

Herald rules similar to what is described in T140605 will be needed as well.

Event Timeline

Language October–December 2016

@Amire80: I guess that is supposed to be "Language-Engineering October–December 2016" instead?

For the sprint projects, please check whether subprojects or milestones might be more suitable instead of "detached" separate sprint projects. (This might also save us some Herald rules.) Thanks!

We actually already have some discussion with @Amire80 about the possible transition.

Danny_B triaged this task as Medium priority.Aug 9 2016, 5:52 PM

The CX11 release board is not going to be made this time. The remaining are all done. Following herald rules are needed and will be sent over via appropriate ticket request:

  1. All tickets with with sprint tags for Oct-Dec 2016 to automatically include the Language-Engineering October-December 2016 tag
  2. All tickets with existing CX-* tags to automatically include the ContentTranslation tag
Amire80 added a subscriber: • Arrbee.

We do still need the Herald rules for all the language-q2-2016-17_sprint_* tags, so that adding them will automatically add the Language-Engineering October-December 2016 tag.

Can we disable {H179} for Jul-Oct2016, created in T140605?

Created {H191}:

Can we disable {H179} for Jul-Oct2016, created in T140605?

Not yet, but some time soon when I finish cleaning up this quarter.

Created {H191}:

The description looks right, but when I tried adding Language-Q2-2016-17 Sprint 1 to T139332, it didn't seem to work.

  1. All tickets with existing CX-* tags to automatically include the ContentTranslation tag

Created {H192}:

Closing as resolved.

(Please strongly consider using subprojects and milestones for 2017.)

If you want to mass-add ContentTranslation to any existing tasks in CX-* projects, please batch-edit accordingly.

Closing as resolved.

(Please strongly consider using subprojects and milestones for 2017.)

I will, but it still doesn't seem to work. See T139332.

@Amire80: Sorry, my fault. Replaced "all" by "any" in H191. Can you recheck?

@Amire80: Sorry, my fault. Replaced "all" by "any" in H191. Can you recheck?

Aha, now it's done. Thanks!