You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Current »

Date Poll

COMMON-2020AUG Requirements Gathering (UTC Time)

June 2020
Tue 2 Tue 2 Tue 2 Wed 3 Wed 3 Wed 3 Wed 3 Wed 3 Wed 3 Wed 3 Thu 4 Thu 4 Thu 4 Thu 4 Thu 4 Thu 4 Fri 5 Fri 5 Fri 5
3 participants 2 3 2 1 1 1 1 3 3 2 1 2 3 2 3 3 2 2 2

Agenda

Short Term (2020AUG / 2020OCT)

  • Maintenance (Bug-fixing / Improvements) (Ralph) As ALMA is shutdown is this expected to take much time?
    • (Tomas) It is true that almost no new tickets have been created, but we still do have an interesting backlog
    • key summary type created updated due assignee reporter priority status resolution

      Unable to locate Jira server for this macro. It may be due to Application Link configuration.


  • Test Cases Stabilization (~15 remaining tests) – 2020AUG / 2020OCT
  • Makefile Refactoring Pending Tasks – 2020AUG
  • RHEL / CentOS 8 Support – 2020OCT
    • Should be 1 week of effort at most
  • Investigate BulkDataNT upgrade to latest RTI DDS version (Ralph) what is motivating this upgrade?
    • (Tomas) Several BulkData Issues, renewing license process, avoid obsolescence, etc.
  • Investigate problem with BulkDataNT and 2 NICs
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Homogenize logs sent to XML files and Kafka (Ralph) Is there a ticket on this?
    • (Tomas) Will be created by Johnny
  • ComponentCaller to handle methods with Callbacks (Ralph) Is there a ticket on this?
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • (Ralph) The last planning meeting added "BulkDataNT: Check data rate behavior with unreliable receiver configured with different qos_profile instead of a different qos_library". Was this done, dropped or overlooked?
    • (Tomas) We're working on this aiming to do it before Monday (2020JUN Pre Release)
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • TMCDB Changes
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration. ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  –  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Mid Term (2020 DEC --> 2021APR)

  • Finish ACS Makefile Refactoring – 2020DEC / 2021JAN
    • Restart efforts with other subsystems
  • Redesign Notification Service – 2020DEC
  • TMCDB Split analysis – 2020DEC
    • (Ralph) The split analysis has been done by Alexis (ICT-9558 comment dated 2017-07-11). Getting this done for cycle 8 will reduce the number of mandatory back-ports. Can the split be completed before 2021FEB?
  • ACS and Java Modules (Just allowing the usage, no porting whatsoever) – 2021FEB

Long Term (TBD)

  • ACS and Java Modules
  • ACS C++ Thread modernization – ~2021JUN
  • Redesign C++ Logging

Other Input

  • TMCDB changes that will be needed to support the ACA Spectrometer

Conclusions

2020AUG

  • *Maintenance – Bug Fixing / Improvements
  • *Test Cases Stabilization
  • *Makefile Refactoring
  • *BulkDataNT Investigations
  • *Start working on TMCDB changes (including split)

* Tentative base for 2020AUG until the meeting has been held

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Action Items

  • Type your task here, using "@" to assign to a user and "//" to select a due date
  • No labels