Page History

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-701

  Planned end: Jun/09/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-699

  Planned end: Jun/03/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-695

  Planned end: Jul/31/2020

• RFC-701: just new still discussions ongoing
  • no actions to be taken today
• RFC-699: discussion converging, it should be just up to Tim Jenness
  • postponed to next week
• RFC-695: still plenty of time to discuss it (end of July)
  •  Leanne Guy to check if the end date of RFC-695 is driven by some specific factor  – it was an arbitrary choice meant to indicate that it was not urgent on the 2-week timescale. I will review the science driver and update the ticket.

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-700

  Planned end: Jun/12/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-698

  Planned end: Jun/24/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-697

  Planned end: May/29/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-680

  Planned end: Apr/01/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-652

  Planned end: Jan/22/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-651

  Planned end: Jan/22/2020

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-638

  Planned end: Jun/7/2021

• RFC-700 Flagged
• RFC-698 KT
• RFC-697 transparent for CCB
• RFC-680 should just be adopted
  • John Swinbank to ping the assignee
• RFC-652
  • Flagged
• RFC-651
  • Flagged
• RFC-638, long term discussion

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-333

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-640

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-686

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-696

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-689

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-693

• Jira
  server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-31

• Next planned major release 20.0.0

  • Planned for Spring 2020
    

    Jira
    server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-20564

  • No blocking issues open.
    • w_2020_21 had a blocking issue
      

      • Jira
        server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-25149

    • Is the w_2020_22 ready to go?

      • Jira
        server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-25177

         could be ported to the first or second release candidate
  • Community Post Status and Discussion https://community.lsst.org/t/science-pipeline-release-20-0-0-status-and-discussion/4126

• The problems found on w22 should come out on the weekly assessments
• Leanne Guy Why those problems are not highlighted by unit and regression testing?
  
  • The reference date is changing and therefore is difficult to catch these type of problems
  • Large datasets are required
• 4 3 issues blocking the release candidate
• John Swinbank  can do the backport
• Kian-Tat Lim : has something been added sine w22?
  • the default answer if no
• DMCCB decided to go with w22 and do backport.

Support to J. Swinbank monitoring activity.

1. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-7102

2. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8958

3. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8974

4. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8987

5. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-7257

6. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-7806

7. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8998

8. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8988

9. Jira
   server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-2517

10. Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-8655

3950 unresolved issues (3928 on May the27th)