Hi Julian I think a higher frequency release is not an issue. You just need to have enough PMC members to vote. Compiling, LICENSE, sign checks are the key, instead, the feature tests and whether you are releasing a stable release, that is PMC's call. The minimal time requirement is only 3 days to make global people having a chance to check the release. This should not stop the community to do a weekly release.
SkyWalking doesn't do a weekly release every month, but due to 10+ subprojects, it is common we do 1-2 releases weekly. Sheng Wu 吴晟 Twitter, wusheng1108 Julian Hyde <jh...@apache.org> 于2021年5月2日周日 上午3:15写道： > 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 > >
