Hmm, I like the ability to look at a project’s snapshots and know which version is going to be published next. It also means that users can add a dependency on a snapshot version and get regular updates with a potential upper bound to the latest version that will be picked up.
Mike Collado > On Dec 2, 2025, at 5:18 PM, Yufei Gu <[email protected]> wrote: > > I like the simplicity of the proposal. That said, I do have a small > concern: the nightly builds rely on using the next version, and bumping the > version every ~1.5 months hasn’t really been a major overhead for us. It’s > been pretty manageable in practice. > > There’s also a minor benefit to keeping main on the next version, which > provides a clear message to contributors about the next version the > community is heading. > > Overall, I’m open to improvements, but I’m not fully convinced the fixed > version buys us enough given the trade-offs. Happy to hear others’ thoughts! > > Yufei > > >> On Tue, Dec 2, 2025 at 11:43 AM Dmitri Bourlatchkov <[email protected]> >> wrote: >> >> Hi All, >> >> Using a fixed version on `main` sounds reasonable to me. However, we may >> need to use three components to be compatible with SemVer. >> >> How about `99.0.0-SNAPSHOT` ? (two 9's for brevity) >> >> Cheers, >> Dmitri. >> >>> On Tue, Dec 2, 2025 at 6:29 AM Robert Stupp <[email protected]> wrote: >>> >>> Hi all, >>> >>> The version on the main branch is currently >>> '1.3.0-incubating-SNAPSHOT', with a PR to bump it to >>> '1.4.0-incubating-SNAPSHOT'. >>> >>> I'd like to propose to "fix" the version on the main branch to some >>> value and just skip the "async" version bumps on the main branch. >>> For example, set it to '999-SNAPSHOT' once and never care about >>> "fixing" the main branch before/with/after every release. >>> >>> WDYT? >>> >>> Robert >>> >>
