-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Release v1.50.0 #892
Comments
Thanks a lot for this, looks good, acknowledge. I think we can announce for Monday if @Surfict has no objections. For some commits I currently dont have the full information, but maybe @Surfict and @sanderegg are in sync. @sanderegg could you possibly add in
|
@mrnicegyu11 I created that one: https://git.speag.com/oSparc/osparc-ops-environments/-/issues/479 the other day. sorry forgot to tag you there. I will add the values I think should go there. |
this was the info I was missing, veyr diligent thanks a lot! good2go for the release from my side, we can announce
|
@mrnicegyu11 the issue is updated now |
@sanderegg why this is labeled with Feedback? I would also like to discuss with you about labeling and the meaning (e.g. maintenance vs enhancement?) |
@pcrespov was a mistake. |
Due to changes in ITISFoundation/osparc-simcore#3883:
If a service requires access to the internet like s4l based services (license server), they need forwarding rules that are valid. Currently prod aws is the only one which can use the current rules on the labels. |
|
Ops changes :
|
In preparation for release. Here an initial (incomplete) list of tasks to prepare before releasing:
Motivation
Check changelog 🚨
Full Changelog: ITISFoundation/osparc-simcore@v1.49.0...v1.50.0
Check devops⚠️
Test assessment: e2e-testing 🧪
dalco-staging
aws-staging
Regarding the s4l-lite above:
@mguidon : Failing tests in staging due to hardcoded-label to production license service (see comment below by @GitHK )


After adding full-access to all groups (only for staging) tests returned to green. NOTE @pcrespov that these changes have to be reverted once the osparc environment identifiers are in place !
Test assessment: targeted-testing 🔍️
Test assessment: user-testing 🧐
Release summary
{"start": "2023-03-06T13:00:00.000Z", "end": "2023-03-06T15:00:00.000Z", "reason": "Release v1.50.0 "}
Release assessment
https://github.com/ITISFoundation/osparc-simcore/releases/tag/v1.50.0
The text was updated successfully, but these errors were encountered: