> Just a suggestion: If we’re concerned about interfaces and UX, why don’t we release it as a 0.x version so we can release now and also more easily implement UX changes based on feedback?
Good idea. That might be a good way of doing it indeed. Seems like releasing something like airflow-ctl as "beta" does not yield enough of an interest to do testing and "api review" - seems like only RCs started to get attention - and having a "released" version might make even more end users start looking at it, having comments and opinions - and 0.* even in semver means "changes will happen". On Fri, Oct 31, 2025 at 12:04 AM constance.astronomer.io via dev < [email protected]> wrote: > Just a suggestion: If we’re concerned about interfaces and UX, why don’t > we release it as a 0.x version so we can release now and also more easily > implement UX changes based on feedback? > > > On Oct 30, 2025, at 5:28 PM, Ash Berlin-Taylor <[email protected]> wrote: > > > > > > > >> On 30 Oct 2025, at 19:03, Buğra Öztürk <[email protected]> wrote: > >> > >> For the last part you raised, dagrun-dag command shift, pause-unpause. > >> These are for sure a breaking change, and we cannot change until 2.0 > > > > We can’t change it until 2.0 if we release it as it stands. Hiwever > since we haven’t released it yet we can still change it now before a 1.0 > release is final (i.e. e have the option to cancel/close this vote, make > some changes then have another rc and vote later) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
