Thanks, Jarek! That’s a great point. I will add a short note in the release documentation of airflowctl about the versions we’re using which should help avoid any confusion in the future.
Bugra Ozturk On 2025/10/31 19:00:10 Jarek Potiuk wrote: > This vote has been cancelled. As discussed and decided by Bugra - we will: > > * address some of the concerns on possibly future breaking changes > * change the version to 0.* > * start a new release vote after > > One (small and not very significant) consequence of that is that we already > had 1.0.0rc1 and 1.0.0rc3 released in PyPI and this means that we will not > be able to do 1.0.0rc1 and 1.0.0rc2 in the future because of PyPI > "write-once-only" approach (even if you delete a package version - you > cannot re-upload another package with the exact same version). > > This means that when we get to 1.0.0 - we will have to start with rc3. And > this is something we will have to remember and not be surprised by it. > > In the meantime I will yank 1.0.0rc1 and 1.0.0rc2 - with appropriate > comment - this will reduce future confusion for people who might think this > is "future" 1.0.0 after we release 0.* version. > > J. > > > On Fri, Oct 31, 2025 at 7:53 PM Jarek Potiuk <[email protected]> wrote: > > > Cool. Cancelling the vote then ! Fantastic outcome of the discussion ! > > > > On Fri, Oct 31, 2025 at 4:55 PM Daniel Standish via dev < > > [email protected]> wrote: > > > >> I like 0.* too. I think this gives us flexibility to make changes and > >> adjust while it's new. I think it's very wise. > >> > >> On Fri, Oct 31, 2025 at 8:54 AM Buğra Öztürk <[email protected]> > >> wrote: > >> > >> > It’s a great idea, Constance. Thanks a lot! This approach will > >> definitely > >> > help us release faster, and we can aim for version 1.0 once we reach > >> > consensus and ideally have no -1 votes, ensuring the best experience. > >> This > >> > will help us to collect more feedback and even allow users to be > >> informed > >> > as well. > >> > > >> > > >> > Thanks again, Jarek, for your help with the release process! Let’s go > >> ahead > >> > and cancel the current voting. If we’re all aligned on continuing with > >> the > >> > 0.* versions first, I’ll update the version before the next vote. I’ll > >> also > >> > follow up on the breaking changes discussed in this round before the > >> first > >> > 0.* RC voting. We can move ahead in a day or two and cut the RC for the > >> > first 0.* release. We can target cutting again around Sunday or Monday > >> for > >> > 0.*. > >> > > >> > Let’s keep the interface and UX updates for later 0.* releases, > >> definitely > >> > before 1.0 (which isn't far away, considering the comments shouldn't > >> take a > >> > long time to address and hopefully we will have more feedback to > >> improve), > >> > where we can gather more opinions and feedback from everyone. > >> > > >> > What do you think? > >> > > >> > On Fri, Oct 31, 2025 at 12:57 AM Jarek Potiuk <[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? > >> > > > >> > > 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] > >> > > > > >> > > > > >> > > > >> > > >> > > >> > -- > >> > Bugra Ozturk > >> > > >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
