Project

General

Profile

action #42914

action #40475: [functional][y][saga] Establish YaST team split

action #42191: [functional][y][epic] Have separate job group for YaST subteam

[functional][y][u] Update review workflow for split domains

Added by okurz over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA tests - Milestone 22
Start date:
2018-10-25
Due date:
2019-01-15
% Done:

0%

Estimated time:
Difficulty:
Duration: 59

Description

Motivation

After having specific job groups for the corresponding subteams we should ensure a proper review workflow is attached to that

Acceptance criteria

Suggestions

  • DONE: Rename "autoyast" section on wiki page to "yast"
  • Decide within each subteam how a daily review is ensured, e.g. based on leader+supporter per day or differently

History

#1 Updated by riafarov over 1 year ago

  • Due date set to 2018-11-20
  • Priority changed from Normal to High

#2 Updated by okurz over 1 year ago

  • Description updated (diff)
  • Status changed from Workable to Feedback
  • Assignee set to okurz

Discussed in the daily 2018-10-30 with QSF. Updated https://wiki.microfocus.net/index.php?title=RD-OPS_QA%2FopenQA_review&type=revision&diff=375641&oldid=375317 including a schedule proposal. So the first suggestion about renaming the "autoyast" section is actually done already.

Further proposals:

We try to focus the subteams ''QSF-u'' and ''QSF-y'' more which should also be reflected by daily test review domains. The following options (''O'') are considered:

  • O1: We emphasize the ''areas of expertise'' including the YaST job group as one of them but keep a QSF team-wide weekly-schedule with overlap of u-/y-team members
  • O2a: Have a shared, overlap weekly-schedule for o3 and per subteam for osd
  • O2b: Have a schedule per subteam and let ''QSF-u'' handle o3 review (''con:'' y-team would loose early feedback from new YaST development related changes, especially when SLE products go into hardening phase, ''pro:'' more focus for y-team)
  • O3c: As above but ''QSF-y'' handles o3 (''pro:'' y-team closer to YaST development as they would like to be, ''con:'' userspace failures challenging for QSF-y)
  • O4: No daily review of o3 anymore, just areas of expertise -> okurz: Not acceptable as the very efficient openSUSE test review approach where oS RMs do the main share of the work should not be hindered by additional frustration when they need to handle the test breakages we introduce or the yast related changes that we already know about

@team WDYT? Feedback welcome!

#3 Updated by riafarov over 1 year ago

  • Due date changed from 2018-11-20 to 2018-12-04

TBD in today's retro.

#4 Updated by mgriessmeier over 1 year ago

O1 sounds really reasonable for me - even though I have concerns about losing coverage

#5 Updated by okurz over 1 year ago

Discussed in the QSF retrospective. We are fine for now with O1, that is we keep a sub-team overlapping schedule for now.

Minor specific proposals:

  • Add jrivrain to the daily schedule
  • Add oorlov to the overlap schedule replacing jrivera
  • Try out review on a weekly base, not daily -> we did a short poll on that, some +1, some -1, some undecided

#6 Updated by okurz over 1 year ago

done with https://wiki.microfocus.net/index.php?title=RD-OPS_QA%2FopenQA_review&type=revision&diff=376355&oldid=376268 but I have another proposal for the y-team daily schedule on the wiki

#7 Updated by okurz over 1 year ago

  • Target version changed from Milestone 20 to Milestone 21

waiting for feedback on my proposal. Maybe we can cover it in one of the next retrospective meetings.

#8 Updated by riafarov over 1 year ago

  • Due date changed from 2018-12-04 to 2018-12-18

#9 Updated by okurz over 1 year ago

  • Assignee changed from okurz to oorlov

oorlov, riafarov, you wanted to come up with a new schedule proposal, right?

#10 Updated by riafarov over 1 year ago

We wanted to make random schedule during the daily last week, but failed to do so. Now quite some people will be on vacation, therefore we need to either wait or come up with the schedule with some people missing.

#11 Updated by riafarov over 1 year ago

  • Due date changed from 2018-12-18 to 2019-01-15
  • Target version changed from Milestone 21 to Milestone 22

Team members are on vacation, so planning for the second week of January.

#12 Updated by oorlov over 1 year ago

Randomizer decision:

u-team:

  1. slindomansilla
  2. dheidler
  3. szarate (foursixnine)
  4. zluo
  5. jrauch

y-team:

  1. mloviska
  2. oorlov
  3. jrivera
  4. riafarov
  5. JRivrain

#13 Updated by oorlov over 1 year ago

  • Status changed from Feedback to In Progress
  • Assignee changed from oorlov to riafarov

#14 Updated by riafarov over 1 year ago

  • Status changed from In Progress to Resolved
  • Assignee changed from riafarov to oorlov

Also available in: Atom PDF