Track request '0' for cos-registration-agent

store-requests tracks
1

We are releasing an initial version of the cos-registration-agent prior to issuing an actual proper release. To avoid breaking existing setups, we want to use the 0 track until then.

This request is on the behalf of the Robotics team.

Thanks!

2

Hi, Per Process for aliases, auto-connections and tracks, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days. I have three questions before casting my vote.

  • What’s the package’s release cadence, how often is a new major version (potentially requiring a new track) released? Is this documented somewhere by upstream?

  • Is there some commitment from upstream on maintenance of old versions? e.g. is the “0.1” release still supported with security updates? Will it continue to be supported now that e.g. “0.2” is out, and for how long?

  • Are new versions backwards-incompatible? Meaning, if I was running “0.1” and try to install “0.2”, will that just work, or do I need to migrate my data/configuration, or will things break horribly?

Thanks,

Shweta

3

Hi @kodoroki ,

See my answer here → Track request '0' for ros2-exporter-agent - #3 by artivis

4

Hello,

My apologies for the wrong ping in my previous message. @shweta1572 the rational for this request is the same I have exposed in Track request '0' for ros2-exporter-agent - #3 by artivis.

5

Thank you for all the information. The track ‘0’ has been created.

Regards,

Shweta

1 Like