The main release burden I have in mind is related to LICENSE/NOTICE generation and verification that is quite complex when it comes to binaries. It's not about signing archives or testing the installers.
On every release vote the majority of my time is spent on verifying compliance of LICENSE/NOTICE with ASF guidelines. I am not doing it for standalone metastore archives and I don't think I will find time to do it for other binaries. Best, Stamatis On Tue, Aug 25, 2026 at 11:14 AM Denys Kuzmenko <[email protected]> wrote: > Hi Team, > > +1 for the initiative. > > I think adding Beeline native installers as convenient binaries would > provide a much better experience for users and should not add significant > overhead to the release process. As Illia pointed out, this would require > only an additional PGP signing step, with the installers distributed > alongside the other release artifacts. > > We could also add CI coverage to build and validate the installers for the > supported platforms, reducing the risk of issues during the release process. > > Overall, the additional release burden seems reasonable compared to the > convenience and accessibility this would provide to Beeline users. > > Best regards, > Denys >
