Skip to content
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

v1.5.1 Hotfix Release Checklist #3939

Closed
11 tasks done
berndverst opened this issue Nov 24, 2021 · 9 comments
Closed
11 tasks done

v1.5.1 Hotfix Release Checklist #3939

berndverst opened this issue Nov 24, 2021 · 9 comments
Labels
hotfix Hotfix releases

Comments

@berndverst
Copy link
Member

berndverst commented Nov 24, 2021

  • Create the v1.5.1-rc.1 Hotfix release (code changes) and test it
  • Create v1.5.1-rc.1 Tag [@berndverst ]
  • Performance tests passing [@artursouza]
  • End to End tests passing on Linux and Windows [@berndverst]
  • Notify users to try RC1
  • Update the longhaul tests to use 1.5.1-rc.1 [@halspang]
  • Release notes
  • Wait until Dec 6th for feedback on RC1
  • Create v1.5.1 Tag [@berndverst]
  • Update the documentation: Latest version & versions in supported releases [@greenie-msft]
  • Announce the hotfix release [@greenie-msft ]
@berndverst
Copy link
Member Author

berndverst commented Nov 24, 2021

PRs required for this Hotfix release.

Make sure to use release-1.5 branches only!

Components Contrib

Dapr/Dapr

CLI

Create new Components-Contrib tag and release.

  • RC tag created
  • Update dapr/dapr go.mod to point to the components contrib release candidate tag
  • Release tag created
  • Release created

@berndverst
Copy link
Member Author

berndverst commented Nov 24, 2021

If this issue gets addressed in time we will also cherry-pick it into the hotfix release:
#3930

@darren-wang
Copy link

@berndverst we found resource leakage in tests before adoption of dapr, now we are waiting the hotfix version, can you cherry pick this pr in 1.5.1?

#3890

Now our adoption process is stuck due to this bug.

@yaron2
Copy link
Member

yaron2 commented Nov 26, 2021

@berndverst we found resource leakage in tests before adoption of dapr, now we are waiting the hotfix version, can you cherry pick this pr in 1.5.1?

#3890

Now our adoption process is stuck due to this bug.

See my comment on the PR: I need to understand if this is a regression (have you not seen this with 1.4.x), and want to understand exactly what the impact is and under which conditions it occurs.

@rabollin
Copy link
Contributor

@berndverst #3930 based on your comment, has someone taken this to fix for 1.6?

@berndverst
Copy link
Member Author

@rabollin doesn't look like anyone is working on it yet, so it isn't likely to make it into 1.5.1. Hopefully someone will take a look for 1.6.

@berndverst
Copy link
Member Author

Yes @darren-wang per the discussion on #3890 and the support from @yaron2 for cherry-picking this, it will be included in the 1.5.1 hotfix release.

@darren-wang
Copy link

Yes @darren-wang per the discussion on #3890 and the support from @yaron2 for cherry-picking this, it will be included in the 1.5.1 hotfix release.

Hi, when is v1.5.1 planned to release?

@yaron2
Copy link
Member

yaron2 commented Dec 1, 2021

Yes @darren-wang per the discussion on #3890 and the support from @yaron2 for cherry-picking this, it will be included in the 1.5.1 hotfix release.

Hi, when is v1.5.1 planned to release?

Dec 6.

@msfussell msfussell added the hotfix Hotfix releases label Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotfix Hotfix releases
Projects
None yet
Development

No branches or pull requests

5 participants