-
Notifications
You must be signed in to change notification settings - Fork 669
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
Roadmap and ideas #281
Roadmap and ideas #281
Conversation
|
||
Living Roadmap | ||
=============== | ||
We are trying to maintain a Living roadmap `here <https://docs.google.com/spreadsheets/d/1V8DQfcsX_02Zac5EfAo0UrGJtLwdMPcw3wuuigVIMZU/edit?usp=sharing>`_ |
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.
Perhaps some treatment on how the open source community can voice their opinion and get things added to the roadmap? Should they open GitHub issues? Will they be required to defend their ideas in the weekly meetings?
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.
agreed, lets add something
|
||
2. Bug Fixes & Reliability Improvements | ||
---------------------------------------- | ||
As mentioned since Flyte is being actively used at Lyft and our scale is always increasing, there are always bugs that we want to squish. So Bugs, are always work in progress and most often then |
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 makes it feel like bugs are a low priority, which isn't always the case depending on the severity of the bug.
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.
really, I feel this says bugs are found and fixed continuously, but maybe we need to create a process of ranking. I do not want to say we will get to them ASAP, as we have not done that
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
Co-Authored-By: Yee Hing Tong <[email protected]>
…atch (flyteorg#281) * FlytePropeller should ignore if Admin is already in terminal state Signed-off-by: Ketan Umare <[email protected]> * Lint fixes Signed-off-by: Ketan Umare <[email protected]>
Same as flyteorg/datacatalog#56 Signed-off-by: stephen batifol <[email protected]>
…lyteorg#281) Signed-off-by: Kevin Su <[email protected]>
…flyteorg#282) Signed-off-by: Nastya Rusina <[email protected]>
# [0.42.0](http://github.com/lyft/flyteconsole/compare/v0.41.0...v0.42.0) (2022-02-10) ### Features * **flyteorg#281:** allow to collapse/expand workflow version section ([flyteorg#282](http://github.com/lyft/flyteconsole/issues/282)) ([a4ac862](http://github.com/lyft/flyteconsole/commit/a4ac8627280f6793113d7538023a6644cf43f429)), closes [flyteorg#281](http://github.com/lyft/flyteconsole/issues/281)
Signed-off-by: Yuvraj <[email protected]>
…atch (flyteorg#281) * FlytePropeller should ignore if Admin is already in terminal state Signed-off-by: Ketan Umare <[email protected]> * Lint fixes Signed-off-by: Ketan Umare <[email protected]>
Same as flyteorg/datacatalog#56 Signed-off-by: stephen batifol <[email protected]>
…lyteorg#281) Signed-off-by: Kevin Su <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
## Overview * go.mod and go.sum are auto-updated on latest master branch ## Test Plan *TODO: Summarize tests added, integration tests run, or other steps you took to validate this change. Include (or link to) relevant test output or screenshots.* ## Rollout Plan (if applicable) *TODO: Describe any deployment or compatibility considerations for rolling out this change.* ## Upstream Changes Should this change be upstreamed to OSS (flyteorg/flyte)? If so, please check this box for auditing. Note, this is the responsibility of each developer. See [this guide](https://unionai.atlassian.net/wiki/spaces/ENG/pages/447610883/Flyte+-+Union+Cloud+Development+Runbook/#When-are-versions-updated%3F). - [ ] To be upstreamed ## Issue *TODO: Link Linear issue(s) using [magic words](https://linear.app/docs/github#magic-words). `fixes` will move to merged status, while `ref` will only link the PR.* ## Checklist * [ ] Added tests * [ ] Ran a deploy dry run and shared the terraform plan * [ ] Added logging and metrics * [ ] Updated [dashboards](https://unionai.grafana.net/dashboards) and [alerts](https://unionai.grafana.net/alerting/list) * [ ] Updated documentation
Updated the docs to have a roadmap section, also created a roadmap Spreadsheet and a ideas document