-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
New Release - proposing 3.0.0 stable #2029
Comments
@DirectXMan12, @estroz, @pwittrock, @Adirio wdyt? Can we move forward here? |
|
Hi @DirectXMan12, @estroz, @Adirio, @joelanford, I see that we have 2 options here which are: Plan A
Plan B
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? |
Version 3 took a really long time so waiting for version 4 may be too far so I'm voting plan B. |
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 |
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. |
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. |
@camilamacedo86 Have you planned to release version 3 soon? |
Hi @HamzaZo, Yes. It is planned to:
|
it is done . |
Following the changelog: (By following the guidance in: https://github.com/kubernetes-sigs/kubebuilder/blob/master/RELEASE.md#release-process)
✨ New Features
go/v3-alpha
) #1758)🐛 Bug Fixes
[kind]_types.go
(🐛 Use correct file name in the comments of[kind]_types.go
#1927)❓ Sort these by hand
pkg/model/file.ProjectNameMixin
(plugins: change project name config tag, addpkg/model/file.ProjectNameMixin
#1609)project-name
config key and optionalinit --project-name
(config: addproject-name
config key and optionalinit --project-name
#1603)v3-alpha
(pkg/plugin/v3: add pluginv3-alpha
#1551)--plugins
/layout
value by semantic version (pkg/cli: resolve--plugins
/layout
value by semantic version #1536)Thanks to all our contributors!
The text was updated successfully, but these errors were encountered: