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.

Sign up for GitHub

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

Jump to bottom

New Release - proposing 3.0.0 stable #2029

Closed
camilamacedo86 opened this issue Feb 18, 2021 · 11 comments
Closed

New Release - proposing 3.0.0 stable #2029

camilamacedo86 opened this issue Feb 18, 2021 · 11 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v3.0.0

Comments

@camilamacedo86
Copy link
Member

camilamacedo86 commented Feb 18, 2021 •
edited

Following the changelog: (By following the guidance in: https://github.com/kubernetes-sigs/kubebuilder/blob/master/RELEASE.md#release-process)

⚠️ Breaking Changes

✨ New Features

🐛 Bug Fixes

❓ Sort these by hand

Thanks to all our contributors!
@camilamacedo86 camilamacedo86 added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 18, 2021
@camilamacedo86
Copy link
Member Author

@DirectXMan12, @estroz, @pwittrock, @Adirio wdyt? Can we move forward here?

@camilamacedo86
Copy link
Member Author

  • raise in the controller-meeting
  • we might want to clean up the changelog as well.

@camilamacedo86 camilamacedo86 added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Feb 23, 2021
@camilamacedo86 camilamacedo86 added this to the v3.0.0 milestone Feb 23, 2021
@camilamacedo86
Copy link
Member Author

camilamacedo86 commented Feb 26, 2021 •
edited

It has been discussed on slack.
We might decide to add as a pre-requirement the changes in the API which allow plugin chains. More info; #2016 and #2043

@camilamacedo86
Copy link
Member Author

camilamacedo86 commented Feb 27, 2021 •
edited

Hi @DirectXMan12, @estroz, @Adirio, @joelanford,

I see that we have 2 options here which are:

Plan A

  • Release 3.0.0: now with the preliminary plugin system and all changes made so far which allow users to start to work with the latest API's as well and is very stable.
  • Release 3.1.0: with the controller-runtime bump 0.8.0
  • Release 4.0.0: with [Meta] Stabilize API for v3.0.0 #2043 - all required/desired changes for plugins chains. Note that the 4.0.0 bump does not allow us to introduce breaking changes in the plugins since they are stabilized either.
    PS.: We might want to bum go 1.16 for 4.0.0 as well.

Plan B

  • Implement all changes in the API regards plugin chains and then we need another beta.1 release for we are able to release the stable one.

If we move with plan A then, I start to think that we might need to create a branch for that to allow @Adirio to move forward easily as well and merge all his PRs. WDYT @Adirio? Also, I think would be better we move with plan A unless we have any restriction to bump sooner 4.0.0.

WDYT?

@Adirio
Copy link
Contributor

Adirio commented Feb 27, 2021

Version 3 took a really long time so waiting for version 4 may be too far so I'm voting plan B.

@camilamacedo86 camilamacedo86 mentioned this issue Mar 2, 2021
Closed
@camilamacedo86
Copy link
Member Author

camilamacedo86 commented Mar 2, 2021 •
edited

Hi @Adirio,

We should not take too long to do the releases. Now, that more people are able to do that we can indeed have a process where we do with more frequency. My concern here is: Has any reason for we are unable to push 4.0.0 with these changes soon? Have we any policy or process which will not allow us to release 3.1 and then 4.0.0 directly?

c/c @DirectXMan12

@Adirio
Copy link
Contributor

Adirio commented Mar 2, 2021

User noise: What would you do if you just updated a project to v3, which is pretty complex, and 2 months later they tell you that v4 is released? You would probably not even look at the changes needed, which may be none, and skip the version bump.

Aside from that (which I think is pretty important), I don't think there is any requirement that prevents it. Let's see what Solly thinks.

@camilamacedo86
Copy link
Member Author

camilamacedo86 commented Mar 2, 2021 •
edited

Hi @Adirio,

It is true. 👍 I agree with the noise and I think you have been doing a great job and we would be very close to moving forward with plan B as well. So, just to clarifies move with plan B is fine for me if we are able to that soon.

@HamzaZo
Copy link

HamzaZo commented Mar 27, 2021

@camilamacedo86 Have you planned to release version 3 soon?

@camilamacedo86
Copy link
Member Author

Hi @HamzaZo,

Yes. It is planned to:

  • release an rc this week
  • and then, the stable released ought to roll out after 2 weeks.

@camilamacedo86
Copy link
Member Author

it is done .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
v3.0.0
Development

No branches or pull requests
3 participants
@Adirio @camilamacedo86 @HamzaZo