Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1850

Support SKA-base class migration to v0.11

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Enabler
    • Should have
    • PI12, PI13
    • None
    • None
    • Services
      • self-help documentation has been added and collated into single document (e.g. PI demos and presentation, API docs, FAQ)
      • Agile teams have been supported when required
    • 0.5
    • 0
    • Team_VULCAN
    • Sprint 5
    • Hide
      • only very few teams were moving to the new version in PI12. On the spot help was given when needed, e.g. CIPA, or in MR reviews of CentralNode updates
      • no integrated documentation has been added as the feedback loop was missing to justify it at this stage. Item has been moved to the backlog to be re-prioritised when teams have scheduled the migration
      Show
      only very few teams were moving to the new version in PI12. On the spot help was given when needed, e.g. CIPA, or in MR reviews of CentralNode updates no integrated documentation has been added as the feedback loop was missing to justify it at this stage. Item has been moved to the backlog to be re-prioritised when teams have scheduled the migration
    • 19.6

    • PI24 - UNCOVERED

    Description

      Support other teams to update to ska_tango_base 0.11, through the provision of documentation, coordination and expert advice.

      ska_tango_base release 0.11 introduced substantial breaking changes including a new device model and breaking updates to the control model. Most LMC subsystems have not yet been updated to ska_tango_base 0.11. It is important that subsystems be updated as soon as possible, so that all LMC subsystems use the same underlying model, in order to simplify integration and deliver improved interoperability and reliability. Providing support to teams as they update will help ensure that the update is achieved as quickly as possible and with minimal effort.

      Attachments

        Issue Links

          relates to

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-80 All artefacts are released and uploaded to the CAR

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1930 Support other teams in take-up of lmc_baseclasses x.11 update (Drew)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Discarded
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                Vani.Naram Naram, Vani
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 0.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete11.0
                  Total11.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel