-
Notifications
You must be signed in to change notification settings - Fork 308
ROADMAP.md update for stages and forward view #2913
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor edits - plus the table is broken - let me know if you want me to fix it up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blocking for markdown lint & url lint issues.
@qnetter let us know if we can help with running those lint checks locally.
Will re-review once resolved.
I'll do it today - no problem. Just wanted to get it checked in before the weekend. |
Mdlint fixes
@joshrosso the urlint fail works fine for me manually - any ideas? |
Co-authored-by: Kay ORiordan <koriordan@vmware.com>
Co-authored-by: Kay ORiordan <koriordan@vmware.com>
Co-authored-by: Kay ORiordan <koriordan@vmware.com>
@qnetter the engineering team is waiting on this roadmap to determine where we should go from here. Do you think we could knock out the formatting asap? Or would you like us to step in and fix the table? |
Fix table.
Last few typos.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few issues pointed out.
The formatted version does reflect the source, but the source has issues. I'm going to update the formatting and push a new commit. |
Signed-off-by: joshrosso <rossoj@vmware.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed formatting; blocking to get feedback from engineering team.
Reworded roadmap discussion guidelines to prioritize Issues and scheduled community meeting sessions.
Split package maintainer item into two
Lots of rewording to reduce duplication, resurface good first issues, etc.
Fixed the date.
Updated release of unmanaged-cluster to 0.10
Fixed awkward Bitnami/kubeapps item.
At some point, the Tanzu Application Platform OSS components in Tanzu Community Edition will include developer dashboards. |
@vmware-tanzu/tce-owners please re-review. |
mdlint fix.
This time mdlint.
I'm totally cool with that... my only comment was if the work isn't being done in the repo, we should point to where the work and/or proposals are being done (ie pointers to issues and proposals in other repos aka Tanzu Framework). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I didn't realize I had to submit before comments could be seen. Sorry that my ignorance caused worry and upset..
ROADMAP.md
Outdated
| |Provide guidance on bringing new provider packages to TCE; enabling the inclusion of new infrastructure providers | Awaiting Proposal (dependent on Tanzu Kubernetes Provider implementation) | TBD | | ||
| |Introduce kubeapps to TCE for discovering and installation packages in Bitnami library [(issue)](https://github.com/vmware-tanzu/community-edition/issues/2418) | Awaiting Proposal | TBD | | ||
| Better defined LCM Cluster API extensibility points |Build the Runtime Extension SDK in Cluster API for ClusterClass patching, pre/post control plane upgrade hooks | Awaiting proposal | TBD | | ||
| Accelerate time to bootstrap Cluster API management clusters | Consider more efficient and resource-saving methods to bootstrap | Awaiting proposal | TBD | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is saying that the project should CONSIDER where the time sinks are in the Cluster-API based process - where time and big resources are spent - and determine with the Framework and upstream teams whether and how we might address them. The work item for now is exploration, not development. Use of CAPI is a requirement from above.
Also, while use of CAPI is a requirement, the actual bootstrap machinery doesn't necessarily have to be a cluster... the management and workload clusters, of course, must be CAPI-managed clusters.
ROADMAP.md
Outdated
| |Provide guidance on bringing new provider packages to TCE; enabling the inclusion of new infrastructure providers | Awaiting Proposal (dependent on Tanzu Kubernetes Provider implementation) | TBD | | ||
| |Introduce kubeapps to TCE for discovering and installation packages in Bitnami library [(issue)](https://github.com/vmware-tanzu/community-edition/issues/2418) | Awaiting Proposal | TBD | | ||
| Better defined LCM Cluster API extensibility points |Build the Runtime Extension SDK in Cluster API for ClusterClass patching, pre/post control plane upgrade hooks | Awaiting proposal | TBD | | ||
| Accelerate time to bootstrap Cluster API management clusters | Consider more efficient and resource-saving methods to bootstrap | Awaiting proposal | TBD | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not following why this theme is separate from
Enhance cloud-native user experience for skilled and new users
, which includes a faster setup time for unmanaged clusters.In my mind, these are similar or the same, but perhaps I'm missing something.
It's an artifact of how it was contributed - they should ands will be merged.
Typos.
Moved CAPI issues to Exploration section and out of table
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hope this goes and the comments were all sent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope comments were received.
@vmware-tanzu/tce-owners Please re-review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My concerns have been addressed.
typos. Thanks @kcoriordan ! Co-authored-by: Kay ORiordan <koriordan@vmware.com>
4c747f2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've decided to merge this and iterate on future suggestions through github issues.
Thanks everyone!
What this PR does / why we need it
This PR updates the published roadmap to include development of features and a more extended forward view.
Details for the Release Notes (PLEASE PROVIDE)
Which issue(s) this PR fixes
Fixes: #
Describe testing done for PR
Validation by core engineering and other stakeholders
Special notes for your reviewer