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.

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

Merged
merged 10 commits into from
Apr 19, 2020
Merged

Roadmap and ideas #281

merged 10 commits into from
Apr 19, 2020

Conversation

kumare3
Copy link
Contributor

@kumare3 kumare3 commented Apr 18, 2020

Updated the docs to have a roadmap section, also created a roadmap Spreadsheet and a ideas document

rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved
rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved

Living Roadmap
===============
We are trying to maintain a Living roadmap `here <https://docs.google.com/spreadsheets/d/1V8DQfcsX_02Zac5EfAo0UrGJtLwdMPcw3wuuigVIMZU/edit?usp=sharing>`_
Copy link
Contributor

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed, lets add something

rsts/introduction/roadmap.rst Outdated Show resolved Hide resolved

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
Copy link
Contributor

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.

Copy link
Contributor Author

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

@kumare3 kumare3 merged commit 0947970 into master Apr 19, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 6, 2022
…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]>
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 6, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Aug 9, 2023
…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]>
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Aug 21, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Aug 21, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Apr 30, 2024
austin362667 pushed a commit to austin362667/flyte that referenced this pull request May 7, 2024
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this pull request Jul 2, 2024
troychiu pushed a commit that referenced this pull request Jul 8, 2024
## 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants