-
Notifications
You must be signed in to change notification settings - Fork 236
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
Project status updates and roadmap #802
Comments
@brokenpip3, thank you so much for stepping up as the maintainer! For those that are struggling to keep their v0.7.1 operator instance running, and are willing to do a bit of pre-release testing, here's a snippet of my
The plugin versions are correct as of today, see #797 |
Hi all, after discussing with the kubernetes and cdf slack admin I created our own gitter channel. Come to say Hi! :) |
Hi all, |
I'm running v0.8.0-beta since yesterday, no problems so far 😎 A small suggestion for future pre-releases: you could name them -beta1 or -rc1 etc in case more than one is needed. |
@rkrzewski thanks a lot for the feedback, very appreciated :) Yes |
Fyi I started working on 0.9 here: https://github.com/jenkinsci/kubernetes-operator/tree/version-9.0, for the moment I only updated (like the original plan) golang from 15 to 20.x and the operator-skd from 1.3.0 to 1.28.0 (following each version upgrade notes) plus most of the golang libraries we use. |
Hi all, We have just released the new 0.8.0-beta.2 version. This release is highly likely to become the stable 0.8.0 version soon, assuming no issues are found. For now, our focus will shift to working on the 0.9.0 version, which will include updates to Golang and the operator-sdk, as mentioned previously. During this time, we will not be introducing any new features. Any new feature development will be planned after the initial release of 0.9.0. Thank you all for your support and stay tuned for further updates! |
@brokenpip3 However, it seems like the default version for workflow-job and git is not compatible with the jenkins version.
But I am happy to see that these 2 imcompatibilties is no longer putting jenkins into a restart loop. |
Hi there. |
it's already considered stable :) |
@brokenpip3 sorry to bother you, but any chance to have 0.8.0 official release soon? Thank you! |
Hi community 👋 A new version is out! https://github.com/jenkinsci/kubernetes-operator/releases/tag/v0.8.1 |
Hi community! 👋
As you may notice I stepped up to try to maintain this project from the previous maintainers.
I'm happy 🚀 about this new role and I will try to do my best to keep this project rolling :)
I want to share with the community what I think should be our new roadmap in order to gather comments, feedbacks and suggestions.
Current situation
Right now the operator is still alive and working against the latest jenkins lts version due to the PRs I made in the past weeks but the overall health is not great, we need to fix some basic stuff (see below) before moving forward and start adding new features.
Future
This is what I thought: (happy to receive any feedback) we should plan 3 new major releases:
v0.8 PR: wip: road to 0.8 #806
This version should be shipped as soon will be possible since the latest release it's ~1y old and should contains:
0.8
issues: https://github.com/jenkinsci/kubernetes-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.8v0.9
This version will be the foundation for the future versions and will contains:
1.15
atm0.9
issues: https://github.com/jenkinsci/kubernetes-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.9v0.10
Finally this will be the version where we can start to add new features starting from some outstanding issues that we have in the repo: https://github.com/jenkinsci/kubernetes-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.10
Community
We are looking for new contributors/maintainers, any help we can get from the community will be great and will help the project to move faster! 🚀
Also we need a new "community" place to discuss, right now we have 2 options:
Like I said any suggestions, criticism and support will be appreciated 🙇
The text was updated successfully, but these errors were encountered: