Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

We had a great conversation on updating the behavior of Flyte retries. I have <https://github.com/flyteorg/flyte/discussions/3793#discussioncomment-6543921|updated the discussion briefly with our decisions> - it would be great to get as much feedback as possible as I know this is a pain-point for many Flyte users.

Also, <@U04H6UUE78B> we were interested in when the correct time to officially transfer this to a formal RFC is? Seems most of the discussion will happen in the incubator and the rest of the process may be for formality?

I'm glad there were great convos!

<@U029U35LRDJ> As per the RFC process in its current version:

&gt; • Starting a Discussion at the <https://github.com/flyteorg/flyte/discussions/new?category=rfc-incubator|RFC Incubator> to gauge interest. Once you have received positive feedback, especially from Maintainers or Steering Committee members, please proceed to:
&gt;     ◦ Ask in the Discussion for confirmation to submit an RFC
&gt;     ◦ If there's no objection (silence is approval) then create an Issue from the Discussion (<https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-discussion|see how>)
&gt;     ◦ Proceed to <https://github.com/flyteorg/flyte/tree/master/rfc#opening-a-pull-request|open a PR>
So, two not-very-time-dependent things should happen to move from incubator to RFC:

1. The idea should receive positive feedback
2. The author should ask and receive no objection to move to RFC
Probably we need to improve on the explicit communication of this things in the actual Discussion to reduce ambiguity