Speaking as PMC of Apache NetBeans, we have a new release every quarter. That’s about as much as one can do for a large project. If you find the requirement to have three people to verify your releases onerous, are you saying that so far less than three people have been verifying your releases thus far? Two? Or one? Sounds a bit dubious to me..
Gj On Sat, 1 May 2021 at 21:15, Julian Hyde <jh...@apache.org> wrote: > Does anyone have any resources/suggestions for making the Apache > release process work smoothly for a community whose culture expects > very frequent releases? > > Some background. I am an ASF member and PMC member of Arrow. I am not > very active in development, but am doing my best to oversee the > project to steer its various sub-communities towards the Apache Way. > > Arrow is a thriving project, by any measure. It has implementations in > several languages, and many contributors will tend to contribute in > just one language, and tend to follow the norms of that language. In > particular, Rust developers expect regular releases (a cadence of one > per week is not uncommon). They also build directly from GitHub (they > don't use a source distribution, or rely on pre-compiled artifacts in > a package repository). > > The Arrow-Rust developers are currently discussing how they might > bring some of that Rust process into Arrow [1]. > > So, two problems arise: > * My understanding is that an Apache release is a source release. It > requires a release manager to build and sign a source distribution, > and at least three people need to download and verify that source > distribution. That is an onerous process to perform every week. > * Suppose we were to make source releases less frequently (say once a > month) but more frequently (say weekly) bless minor versions by > tagging them in GitHub. We would effectively be encouraging downstream > projects to rely on unreleased code, and my understanding is that that > is contrary to Apache release policy. > > My questions: > 1. Are there any languages other than Rust that have a similar process > of building directly from GitHub? > 2. Are there any projects (in Rust or other languages) that have > successfully solved the problem of frequent releases? > > Julian > > [1] > https://docs.google.com/document/d/1QTGah5dkRG0Z6Gny_QCHmqMg7L2HmcbEpRISsfNEhSA/edit > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
