I wanted to thank everyone for their detailed & thoughtful replies in this
thread. The Arrow-Rust community feel that they can streamline the release
process to do a source release every two weeks or so, similar to the processes
for SkyWalking and Airflow mentioned in the thread.
Julian
On 202
Hi Jarek
SkyWalking and Airflow communities always share some similar patterns due
to our modulization pattern for building systems.
I think your way should be good from the foundation perspective.
Meaningwhile in SkyWalking, we rely on auto e2e/unit tests a lot rather
than manual testing.
SkyWalk
Hi Sheng,
We had a similar discussion recently in Apache Airflow, and I think there
are ways you can still follow the Apache Way spirit, follow the
voting process and keep the community involved. And I personally think
involving your community in the release process is the true embodiment of
the "
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
It is community over code in Apache. By having people, beyond tests, verify
your releases, you build a community rather than a bunch of releases. The
releases of your prohect are not the primary point here. It’s about
building a community which means having at least three people to verify
your rele
The Arrow-Rust modules are much smaller than NetBeans. They are
libraries and can be continuously verified by automated tests, and
therefore, from a software quality standpoint, it is possible to
release at any time. But, to this point, the release cadence has been
artificially slowed to about 3 mo
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
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
