How the community works?

Flyte is used actively in production at multiple companies. We pride ourselves at being extremely customer focused and cares deeply about a high quality customer experience. Thus we always prioritize stability, reliability, observability and maintainability over raw feature development. Features are developed usually in response to specific use cases and user scenarios. That being said, we are proactively thinking about the evolution of the system and how we want to keep adapting to changing requirements. Thus most of our changes reflect future development scenarios and in cases where we feel rapid prototyping would enable us to discover potential pitfalls or uncover hidden use cases we would proactively develop features, behind feature flags.

Thus, it is extremely important to let the community know about your use cases and how we could adapt parts of Flyte to meet those requirements. We welcome collaboration and contributions, but please follow our Contribution Guidelines.

Milestones and Releases

Flyte consists of many components and services. In true Agile fashion each service is independently iterated and co-ordiated by maintaing backwards compatible contracts using protobuf defined in idl. Thus components like flytekit, flytepropeller, datacatalog are independently versioned.

We have decided to release a new version of the overall platform in the flyte repo every month. Thus we create one milestone for end of every month which points to a new release of Flyte. This may change in the future, but to match our velocity of development this is our preferred option. Every release will be associated with a CHANGELOG (in the repo).

Change management

To ensure that changes are trackable and the history is explainable, we use a slightly cumbersome but helpful process as follows. Some of these are our immediate goals - Every PR associated with an issue (automatic searchable documentation) - Large PR’s associated with Proposals - Every major change is associated with documentation - Owner files for all repositories

Release Train

  • We tag issues with milestones, every new issue will be associated with the next milestone. If the issue is not completed by the milestone, or the contributor feels it may slip the deadline, they should manually move it to the next milestone. Every issue not removed, will be moved to the next milestone.

  • Every new issue has a “untriaged” label associated with, if we remove this label we should add an assignee. If a contributor is working on the issue, please remove this label.

  • Release indicates a release for overall flyte - marked mostly by a milestone.

  • Flyte release are monthly

  • We may have patch releases eg. 0.1.x in between the monthly releases.

Upcoming Features & Issues

Issues by Theme



Open Issues



Currently known and open bugs


We are always working on bugs. Open a new one here


Issues related to security enhancements

Security issues


All the issues open with our documentation.

Docs issues

Feb 2021, we are completely overhauling our docs. feedback appreciated!


All the new features in development

Features issues


New capabilities, plugins that are being built into Flyte. These could be hosted services, K8s native execution etc

Plugins issues

This is one of the best place to get started contributing to Flyte. Issues with both labels plugins and flytekit refer to purely client side plugins and are the fastest to contribute


These issues deal with performance, reliability and scalability of Flyte

Scale issues

We are always working on these issues and we would love to head feedback about what you would want to change or what should we prioritize


If you are looking to contribute and want a great first issue, look at these issues

Contribute issues

These are the best issues to get started with

Issues by Components



Open Issues



Issues on FlyteConsole (Flytes UI)

flyteconsole issues

These are great issues to get started with


Issues on flytectl (standalone CLI for flyte)

flytectl issues

Great issues to start with