(Removing user@ from cc. I think this is mainly a dev@ issue.) I believe there are some tensions between this process and the Apache process. In particular, Apache releases tend to be a signed source distribution (tarball) that at least three PMC members download and verify. I totally understand why, as Rust developers, you might find that an onerous process and might want to operate in a different way. It makes sense, and I believe we can solve it. Perhaps by using a word other than "release" for high-frequency snapshots.
It is likely that other projects have already run into this problem and have solved it. Therefore I have sent an email to comdev asking for advice [1]. Feel free to join the thread. Julian [1] https://lists.apache.org/thread.html/rf12538ef0f60f7257e63391e5d4962a6156564020c99d3dfb193f4d7%40%3Cdev.community.apache.org%3E On Sat, May 1, 2021 at 4:01 AM Andrew Lamb <al...@influxdata.com> wrote: > > I propose regularly releasing, every 2 weeks, minor and patch releases of > the arrow-rs crate, following the semver versioning scheme used by the rest > of the Rust ecosystem. I have written a proposal[1] describing how this > might work. > > Feedback and comments most welcome. > > Andrew > > [1] > https://docs.google.com/document/d/1QTGah5dkRG0Z6Gny_QCHmqMg7L2HmcbEpRISsfNEhSA/edit
