You're right Ralph, my mistake – apparently I totally missed that page. I will update email templates (of 8 repositories! 🥴) accordingly.
On Sun, Sep 8, 2024 at 12:29 AM Ralph Goers <ralph.go...@dslextreme.com> wrote: > https://www.apache.org/legal/release-policy.html#release-announcements > > Second sentence of the second paragraph. > > | "Announcements must contain a link to the relevant download page > for the source.” > > I quoted this I the discussion email during the vote for RC1. Referencing > the overall web site doesn’t fulfill this requirement. > > However, I either didn’t look carefully enough or the page changed (more > likely the first than the second) as I did not notice that the downloads > page actually does have the specific links for the artifacts. In my first > look I only saw the link to the Logging Services download page. > > Ralph > > > > On Sep 7, 2024, at 7:03 AM, Volkan Yazıcı <vol...@yazi.ci.INVALID> > wrote: > > > > Can you share where “a direct link” requirement for announcements is > > stated, please? I know of no policy for “announcement emails”. Of the > pages > > I know, there is no such requirement: > > > > Distribution policy: > > https://infra.apache.org/release-distribution.html > > Dist. Creation Process: > > https://infra.apache.org/release-publishing.html > > > > The only “link” related requirement I see is the following: > > > > “Website documentation for any Apache product must provide public > download > > links where interested parties may obtain current official source > releases > > and accompanying cryptographic files.” > > > > and we certainly suffice this condition. Website guides users to download > > artifacts and in the announcement email we share a link to the website. > > Hence, AFAIC, we comply with the ASF policy. Our release email getting > > allowed in announce@ also backs this claim up. > > > > Op za 7 sep 2024 om 15:20 schreef Ralph Goers < > ralph.go...@dslextreme.com> > > > >> Literally the only requirement for the announcement is that it contains > a > >> direct link to where the source archive can be downloaded. > >> > >> Personally, I like to contain a synopsis of the release (bug fix, minor > >> enhancements, etc) with 2 or 3 significant items if there are any and > then > >> provide a link to the release notes. > >> > >> Ralph > >> > >>> On Sep 6, 2024, at 11:49 PM, Piotr P. Karwasz <piotr.karw...@gmail.com > > > >> wrote: > >>> > >>> Hi Ralph, > >>> > >>> On Sat, 7 Sept 2024 at 07:00, Ralph Goers <ralph.go...@dslextreme.com> > >> wrote: > >>>> > >>>> As I said previously, you should expect this will NOT get moderated > >> through the ASF announce list. > >>> > >>> The e-mail has the same format as the one I sent for 2.23.0[1] and is > >>> very similar to the one for 3.0.0-alpha1[2]. > >>> > >>> Looking at other announcement emails, we could probably modify ours by: > >>> > >>> * Stripping them of the release notes, except the short intro we write > >>> manually. The entire list of changes can probably be replaced with a > >>> link to the release notes. > >>> * Adding the download and release notes links explicitly. > >>> > >>> What do you think? > >>> > >>> Piotr > >>> > >>> [1] https://lists.apache.org/thread/8fycgpb2k274bc4y8gp1zswy5jpzc2jh > >>> [2] https://lists.apache.org/thread/z3otp9jr9bpo0r732k02g1mdlfkjb3gm > >> > >> > >
