Release 1.1.0 to next #976
Conversation
|
There is a lot to do in the release milestone: https://github.com/Kong/kubernetes-ingress-controller/milestone/8 Why are we progressing towards a release? |
|
We have a couple bugfixes and features that'd we'd originally wanted for 1.0 but weren't included in it (Cassandra removal because we forgot, route SNI support because we needed to rework it a fair bit). The feature changes necessitate a semver minor bump, and I don't want to hold up route SNI any longer because it's an Enterprise request that's been open for a while now. The other items don't have a quick path to completion, so it makes sense to release what we have now and bump those further out. |
f72398f to
785f8d2
Compare
|
Force to update changelog: missed #838 was as it was originally in 1.2, but got PRed and merged in, so it will go out in 1.1. Un-drafting this as we're still targeting this for tomorrow per conversation in chat. Still do not merge until #863 is closed, but anyone can drop the label, whereas only the author can un-draft (I think). |
What this PR does / why we need it:
Releases 1.1.0 to next. Bumps manifest controller version and Makefile version; updates changelog.
Special notes for your reviewer:
This is predicated on both #975 and #863.
This includes both release changes and a merge from main to next, to incorporate the doc migration changes and Enterprise default tag update that occurred after the last merge. #863 will further need a rebase after that and another round of manifest regeneration, so drafting this for now.