Thank you Dan, this is a very clear document I think this is the most important part and worth posting to the mailing list
> The two-year norm also doesn't match what's actually happening in the ecosystem. Some features are entering mainstream usage well ahead of any such window — Variant and the Geo types are being adopted aggressively by writers and engines because the demand is real and immediate. In my opinion, the Apache Parquet mailing list contributors, committers, and PMC does not (and should not) have the luxury of mandating adoption trends (either slower or faster) across the ecosystem. As this point in your document makes clear, there are many Parquet stakeholders, each with different constraints and needs, that will adopt the features at their own rate. We shouldn't be trying to hold them back from using new features. I believe the best thing we can do as a community is foster clear communication that helps implementers make the best decisions for their own adoption. Specifically this is embodied in the "implementation status" page[1] which we can and should continue to evolve to let Parquet users choose the feature set that is right for them Andrew [1]: https://parquet.apache.org/docs/file-format/implementationstatus/ On Mon, Jun 1, 2026 at 5:36 PM Daniel Weeks <[email protected]> wrote: > Hey Parquet Community, > > A few weeks back during one of the community syncs, the topic of versioning > came up (again) and I offered to pull together some thoughts on how we > might want to move forward. > > I've gathered some of the background and concerns about how we address > versioning across the ecosystem in order to have a discussion and gather > feedback. > > There are a lot of new features and major capabilities that community > members are eager to introduce, so it would be great to have a clear path > forward on how to coordinate changes. > > I've included the discussion in a doc > < > https://docs.google.com/document/d/1zrbGT4kRCEdadBUludwfQR9b2CfLgH-RWn9zE84gYfg/edit?tab=t.0#heading=h.aozivdm2oj4d > > > so that people can comment and respond either in-line or on this thread. > > Looking forward to discussion and feedback! > -Dan >
