DSS v0.23.0 release

[wing-utm-sharing-airspace]

What commit is it important for this release to contain?

• aa6ea36
• 1b814af

Requested timing

Requesting a new release candidate for DSS v0.23 ASAP (prefer latest early next week) as the US UTM industry intends on conducting internal testing and release validation on the new DSS release.

Additional context

Similar to the validation that was done for rc2, requesting that the InterUSS team validate performance of rc3 against representatations of the three validation scenarios previously provided in: #1541 (comment).

When this release is cut, would also request the InterUSS team provide additional guidance on upgrade steps and release compatibility, in line with the items requested in: #1598

[mickmis]

FYI we will start effort toward this tomorrow. It should be ready by Wednesday.

[barroco]

@wing-utm-sharing-airspace - Is it ok to rename the issue as DSS v0.23.0-rc3 release ?

We just noted that 1b814af is not yet merged on master. We will provide an update tomorrow in any case.

[wing-utm-sharing-airspace]

Yes, supportive of renaming the issue as such and have done so

[BenjaminPelletier]

As a status update with regard to the two requested commits: the commit that fixes the simple-but-critical bug (aa6ea36) is included in rc3, but the commit in #1523 is not included. If I interpret correctly, the need for that second commit is to resolve #1509 since the intent of #1523 was to address #1509. After additional investigation (see discussions in Issue and PR) and discussion in the meeting today, I believe the need to resolve #1509 is met in rc3 when time-based notification indices are enabled. So, I think rc3 should meet the needs of this Issue if I correctly interpreted them, but please let us know if that isn't accurate.

As an additional note, I believe we expect rc4 shortly (next couple days) from some issues discovered during the release verification process (related to default cloud storage mechanism IIUC).

[mickmis]

I confirm release v0.23.0-rc3 is available: https://github.com/interuss/dss/releases/tag/interuss%2Fdss%2Fv0.23.0-rc3
As @BenjaminPelletier mentions, it contains an issue that could prevent in some cases AWS deployments from being functional. This will be fixed in rc4, to be released this week.

[mickmis]

v0.23.0-rc4 is now available: https://github.com/interuss/dss/releases/tag/interuss%2Fdss%2Fv0.23.0-rc4

@wing-utm-sharing-airspace could you please close this issue if this covers your needs?
Notably regarding @BenjaminPelletier comment above:

After additional investigation (see discussions in Issue and PR) and discussion in the meeting today, I believe the need to resolve #1509 is met in rc3 when time-based notification indices are enabled. So, I think rc3 should meet the needs of this Issue if I correctly interpreted them, but please let us know if that isn't accurate.

Thanks!

[wing-utm-sharing-airspace]

Confirming that the release candidate meets our needs, thank you for the timely response

[BenjaminPelletier]

I'm reopening this Issue since I think there was some miscommunication. One element of this request was:

requesting that the InterUSS team validate performance of rc3 against representatations of the three validation scenarios previously provided in: #1541 (comment).

I do not believe that has yet been performed, so I think the original request is not yet complete. @wing-utm-sharing-airspace if this is no longer needed, could you explicitly verify that element of the request is no longer needed? Otherwise, I believe we will need to provide the results of these three validation scenarios before this Issue can be re-closed.