Hi all, As our community continues to grow, we’ve seen interest from contributors and new committers in understanding the mechanics behind an Apache Polaris release. In the Apache Software Foundation (ASF), a release is not just a technical milestone, but a very formal "Act of the Foundation" that carries legal weight and requires specific community governance.
The process must be very formal, but newcomers often find the reason unclear. Initially I wanted to provide a short write up and post it here on the mailing list, but the amount of information proved too extensive for a quick email. Hence, I created a document, which can be published on our website [3883], detailing the release manager role and relevant background information such as dependencies, licenses, voting, release artifacts and their types, communication. The new document amends/details the brief variant in the previous PR [3874]. Cheers, Robert [3883] https://github.com/apache/polaris/pull/3883 [3874] https://github.com/apache/polaris/pull/3874
