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

releases: Shall we reevaluate the release candence for the 2.4.0 and onwards? #243

Closed
fidencio opened this issue Nov 1, 2021 · 6 comments
Labels
area/community enhancement Improvement to an existing feature needs-decision Requires input from the Architecture Committee

Comments

@fidencio
Copy link
Member

fidencio commented Nov 1, 2021

During a few release cycles we experimented with a shorter cadence for our releases, which combined with the maintainence of only one stable branch, has had some impact on our users.

The current way of handling releases, as described here has made a release life-cycle reasonably short, maybe way too short for some companies taste.

Moving to a longer period could have a negative impact of waiting for too long in order to get something out, and also increasing the maintainence burden on the stable branch, but then companies could be able to rely more on the stable branches.

This, combined with a LTS proposal made some time ago could be explored for finding the right balance between what we currently have and what we may want to do.

/cc @amshinde @bergwolf @egernst @sameo @kata-containers/redhat

@fidencio fidencio added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Nov 1, 2021
@jodh-intel
Copy link
Contributor

+1 to re-evaluating. Sounds like a good topic for the AC meeting. But also, we should explore the question in the user survey to get as much exposure around the question as possible.

@jodh-intel jodh-intel added needs-decision Requires input from the Architecture Committee enhancement Improvement to an existing feature and removed bug Incorrect behaviour labels Nov 1, 2021
@ariel-adam ariel-adam added area/community and removed needs-review Needs to be assessed by the team. labels Nov 16, 2021
@fidencio
Copy link
Member Author

fidencio commented Dec 1, 2021

@fidencio
Copy link
Member Author

After pretty much 2 weeks of the form being out, we had 7 answers: 5 from the architecture committee, one from IBM, one from Red Hat.

With the form we learned that:

  • 57.1% of the voters are not happy with the current release cadence
    • 1 minor release every 12 weeks, 1 patch release every 3 weeks
  • 57.1% of the voters are not happy with the current support time of the stable branch
    • 12 weeks
  • About the minor release cadence ...
    • 28.6% of the voters would prefer a minor release every 24 weeks
    • 28.6% of the voters would prefer a minor release every 12 weeks
      • This is the same as we have Today
    • 14.3% of the voters prefer a minor release every 4 weeks
    • 14.3% of the voters prefer a minor release every 16 weeks
    • 14.3% of the voters chose "other", and stated:
      • 3 months (12 weeks) is fine, but shorter cadence would work as well
  • About the patch release cadence ...
    • 57.1% of the voters prefer a patch release every 4 weeks
    • 28.6% prefer dropping the patch releases entirely
    • 14.3% prefer a patch release every 3 weeks
      • This is what we currently have
  • And about how long the stable branch should be maintained, we got the following feedback:
    • 3 answers with 4 months
    • 2 answers stating that 3 months is fine
    • 1 answer saying 6 months
    • 1 answer saying that there shouldn't be a stable branch at all
    • And one comment that was raised twice is that around major releases, the maintenance of the stable branch should be done for 6, 9, or even 12 months
      • This would cause an overlap and we'd maintain 2 stable branches for a while.

Screenshot from 2021-12-13 20-38-04
Screenshot from 2021-12-13 20-38-14
Screenshot from 2021-12-13 20-38-24
Screenshot from 2021-12-13 20-38-35
Screenshot from 2021-12-13 20-38-52
Screenshot from 2021-12-13 20-39-06

@fidencio
Copy link
Member Author

From what we get from the answers the new model would be:

  • A minor release every 12 weeks --> Same as Today
  • A patch release every 4 weeks --> 1 month more than what we have Today
  • The stable branch should be maintained for 16 weeks --> 1 month fmore than what we have Today, and that would cause an overlap so we end up maintaining 2 stable branches.

My suggestion here is:

  • minor releases: every 16 weeks (4 months)
    • this is the middle ground between the 2 most voted options
    • this means there's a change, as the majority of the voters are not happy with current model
  • patch releases: every 4 weeks (once per month)
  • stable branch is maintained for 16 weeks (4 months)
    • this means there's no overlap between stable branches maintenance

I'd like to hear from @amshinde, @ariel-adam, @bergwolf, @egernst, @sameo, and @skaegi if my proposal is fair.

@fidencio
Copy link
Member Author

During the architecture committee meeting held on Dec 14th, 2021, we agreed on following the suggestion of having minor releases every 4 months, with patch releases happening every month. The stable branch will be maintained for 4 months, and the wiki is already updated (see: https://github.com/kata-containers/community/wiki/Release-Team-Rota).

I'll raise a new issue to update https://github.com/kata-containers/kata-containers/blob/main/docs/Stable-Branch-Strategy.md and I'm closing this one now.

Issue backlog automation moved this from To do to Done Dec 14, 2021
@jodh-intel
Copy link
Contributor

Thanks @fidencio ! Yep, a new table in that doc would summarise that nicely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community enhancement Improvement to an existing feature needs-decision Requires input from the Architecture Committee
Projects
Issue backlog
  
Done
Development

No branches or pull requests

3 participants