Tasks for release v1.2 branch and starting v1.3 cycle

[ykakarap]

Let's wait with implementation until we get close to the release. No action needed at the moment.

Setup CI signal for v1.2

• Create the release branch "release-1.2"

• Create new jobs and dashboard for the release-1.2 branch in test-infra

  • Issue: Create jobs for the release-1.2 branch #6671
  • PR: Add jobs for CAPI release 1.2 kubernetes/test-infra#26621

• Book:

  • Make sure the previous book is available under https://release-1-2.cluster-api.sigs.k8s.io/ and https://cluster-api.sigs.k8s.io/
    • PR: add DNS for CAPI release-1.2 release branch kubernetes/k8s.io#3872
    • Check that certificates are valid
      • Get someone with access to Netlify hit the renew certificate button on Netlify UI.
    • Change production branch in Netlify (might need a new rollout or something)
      • Someone with access to Netlify should "re-deploy" on Netlify UI for the book to start pointing to the new release branch.
  • Update refs in introduction.md (drop unsupported versions, add previous version)
    • PR: 📖 Add release 1.2 book link #6697
  • Add a new migration doc for provider implementers
    • PR: 📖 add v1.2 -> v1.3 migration doc #6698
  • Update clusterctl links in the quickstart
    • PR: 📖 update clusterctl version to v1.2.x in quick start #6716

• Homebrew:

  • Update homebrew formula for clusterctl. Instructions: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/developer/releasing.md#homebrew

• Set EOL date for v1.1: 📖 book: set v1.1.x EOL date #7146

Starting work on v1.3

• GitHub milestone

  • Create the new v1.3 milestone via GitHub UI
  • Update the milestone_applier config accordingly
    • PR: cluster-api: update milestone applier config for v1.3 kubernetes/test-infra#26631
  • Move GitHub issues to the new milestone (schedule triage session @vincepri)
    • Latest discussion on ways to assign milestones: Update Roadmap page in CAPI book #5519 (comment)
    • Moved the item to a new issue: Issue triaging for v1.3.x #6950

• Prepare main branch for v1.3 development:

  • Issue: Prepare main branch for v1.3 development #6833
  • PR updates to v1.2.0-beta.2: 🌱 Bump versions to v1.3 #6834
  • Need follow up PR to update to v1.2.0 once tag is ready. PR: 🌱 bump to v1.2.0 tag for clusterctl upgrade tests #6885

• Check if we should remove previously deprecated code

  • PR: 🌱 Remove code deprecated in v1.2 #6779

• Update supported versions in versions.md

  • PR: 📖 update supported versions for v1.3 #6850

• Jobs:

  • Modify the clusterctl upgrade jobs to test the new release
    • Issue: Adjust clusterctl upgrade jobs for v1.3 #6835
    • PR updates to v1.2.0-beta.2: Update CAPI version for periodic upgrade jobs kubernetes/test-infra#26750
    • Need follow up PR to update to v1.2.0 once tag is ready. PR: use clusterctl v1.2.0 for upgrade tests kubernetes/test-infra#26779

• If we upgrade the apiVersion [DOES NOT APPLY]

  • Add new version of the types:
    • Create new api packages by copying existing packages
    • Make sure webhooks only exist in the latest apiVersion (same for other subpackages like index)
    • Add conversion and conversion tests
    • Adjust generate targets in the Makefile
    • Consider dropping fields deprecated in the previous apiVersion
  • Update import aliases in .golangci.yml
  • Switch other code over to the new version (imports across the code base, e.g. controllers)
    • Add all versions to the schema in the main.go's
  • Add types to the PROJECT files of the respective provider
  • Add test data for the new version in test/e2e/data/{infrastructure-docker,shared} (also update top-level .gitignore)
  • Update docker.yaml, make sure all tests are successful in CI

[ykakarap]

/assign

[fabriziopandini]

/milestone v1.2

[sbueringer]

@ykakarap Looks good, feel free to ping me if you need reviews somewhere :) (or some discussions around when we can do which step)

[sbueringer]

@CecileRobertMichon No rush, but can you write the Netlify folks to fix our cert again? (https://release-1-2.cluster-api.sigs.k8s.io/reference/versions.html).
I would do it, but I don't have access.

[sbueringer]

@ykakarap I opened a PR for the milestone applier (kubernetes/test-infra#26631) to avoid mislabeling PRs to the wrong milestone

[ykakarap]

@ykakarap I opened a PR for the milestone applier (kubernetes/test-infra#26631) to avoid mislabeling PRs to the wrong milestone

Thank you!

[sbueringer]

fyi milestone handling might change for v1.3: #5519 (comment)

[sbueringer]

@ykakarap I think we already did Update supported versions in versions.md at some point for v1.2. We could do the same already for v1.3 and move the task down to the v1.3 section

[ykakarap]

@ykakarap I think we already did Update supported versions in versions.md at some point for v1.2. We could do the same already for v1.3 and move the task down to the v1.3 section

Sounds good. I moved the task down to the v1.3 section.

[sbueringer]

If I see correctly with have PRs for everything and they are on hold until the release, except:

• Update supported versions in versions.md
• Move GitHub issues to the new milestone: Depends on 🌱 improve how do we perform issue triage and milestone management #6828

[ykakarap]

Since we decided to do v1.2.0-beta.2 for the clusterctl upgrade tests for now and go back and do another round of PRs once we have v1.2.0 - those PR should still be considered pending. I will update the task list to update this new information.

Ref: #6834 (comment)

[sbueringer]

I think everything is done except the Github issues.

Given that it depends on #6828, @ykakarap should we move this into a separate issue and close this one?

[ykakarap]

Sounds good. I will create the separate issue, link it here and close this.

[ykakarap]

The new release is out and all the tasks in the list are complete.

The pending item on Github issue triaging is moved to: #6950

/close

[k8s-ci-robot]

@ykakarap: Closing this issue.

In response to this:

The new release is out and all the tasks in the list are complete.

The pending item on Github issue triaging is moved to: #6950

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.