Let us make sure we do this correctly so the hard work you are doing achieves the best result possible.
The Git tag needs to have a comprehensive list of changes since the last tagged release and it must be signed with your signing key for ASF. Please refer to how Josh compiled the 0.20.5-incubating-rc1 tag here: https://github.com/apache/incubator-heron/releases/tag/0.20.5-incubating-rc1 It would be best to keep all of this on the dev@ channel so that we have a reference for the procedure in the future. On Sun, May 8, 2022 at 11:46 AM Nicholas Nezis <[email protected]> wrote: > Oh I thought we were already decided that we wanted to make a release. Most > of the work has been addressing issues found in RC1. I've started making > RC2. I'll continue being the 0.25.5-incubating release manager. Will have a > vote email out today or tomorrow. > > If we need to do something else specific for the RC2 attempt, let me know > and we can do it. > > > On Sat, May 7, 2022, 6:28 PM Saad Ur Rahman <[email protected]> > wrote: > > > I would like to clarify that I am neither creating nor volunteering to be > > the Release Manager. I realize that my previous messages might be > > misconstrued as such. > > > > On Sat, May 7, 2022 at 5:58 PM Saad Ur Rahman <[email protected]> > > wrote: > > > > > I completely agree. It is best to keep the entire process completely > > > public, visible, and auditable. I think the entire team working on > Heron > > > wants this release to be the one we use to complete the incubator > > > requirements. > > > > > > On Sat., May 7, 2022, 5:34 p.m. Josh Fischer, <[email protected]> > > wrote: > > > > > >> it would be good to be explicit and call out that we would like to > make > > a > > >> new release to make sure no one has any concerns. > > >> > > >> If we don’t, it’ll be hard for the community to have any sort of > > >> visibility > > >> into what’s going on. > > >> > > >> On Sat, May 7, 2022 at 4:24 PM Saad Ur Rahman < > [email protected]> > > >> wrote: > > >> > > >> > Hello everyone, > > >> > > > >> > There is a release in progress. To evade any issues with the > release, > > I > > >> > think it is critical we follow the Release Creation Process guide ( > > >> > https://infra.apache.org/release-publishing.html). We have not > > >> completed > > >> > points #2 and #3 as of yet, which I recall Josh completed during the > > >> > previous attempt. > > >> > > > >> > The release policy I read during the previous attempt can be found > > here: > > >> > https://www.apache.org/legal/release-policy.html > > >> > > > >> > There is an Apache Release Audit Tool aimed at helping Podlings in > the > > >> > incubator but it does not support the Bazel build tool: > > >> > https://creadur.apache.org/rat/ > > >> > > > >> -- > > >> Sent from A Mobile Device > > >> > > > > > >
