You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Andreas Beeker <ki...@apache.org> on 2018/07/04 21:24:33 UTC

Announcement wasn't accepted

FYI ... the announcement wasn't accepted, see below comments.

so it looks like, I need to move the files to the location I originally intended.

Andi



-------- Forwarded Message --------
Subject: 	Returned post for announce@apache.org
Date: 	4 Jul 2018 21:15:34 -0000
From: 	announce-owner@apache.org
To: 	kiwiwings@apache.org




Hi! This is the ezmlm program. I'm managing the
announce@apache.org mailing list.

I'm sorry, your message (enclosed) was not accepted by the moderator.
If the moderator has made any comments, they are shown below.

>>>>> -------------------- >>>>>
Announcements of Apache project releases must contain a link to the relevant
download page, which might be hosted on an Apache site or a third party site
such as github.com. [1]

The download page must provide public download links where current official
source releases and accompanying cryptographic files may be obtained. [2]

Links to the download artifacts must support downloads from mirrors. Links
to
metadata (SHA, ASC) must be from https://www.apache.org/dist/<p
roject>/<release>
MD5 is no longer considered useful and should not be used. SHA is required.
Links to KEYS must be from https://www.apache.org/dist/<project>/ not
release
specific.

Announcements that contain a link to the dyn/closer page alone will be
rejected by the moderators.

Announcements that contain a link to a web page that does not include a link
to a mirror to the artifact plus links to the signature and at least one sha
checksum will be rejected.

Announcements that link to dist.apache.org will not be accepted.
Likewise ones which link to SVN or Git code repos.

[1] http://www.apache.org/legal/release-policy.html#release-announcements
[2] https://www.apache.org/dev/release-distribution#download-links

<<<<< -------------------- <<<<<



Re: Announcement wasn't accepted

Posted by sebb <se...@gmail.com>.
I don't think the download directory locations are a problem.

However the download page has several problems:

https://xmlbeans.apache.org/sourceAndBinaries/

- no links to KEYS, sigs, hashes or even release artifacts.
- should not link to unreleased code (ie. no links to SVN)

Have a look at http://cxf.apache.org/download.html for a possible layout
with all the required information.
There are lots of others.


On 4 July 2018 at 22:24, Andreas Beeker <ki...@apache.org> wrote:

> FYI ... the announcement wasn't accepted, see below comments.
>
> so it looks like, I need to move the files to the location I originally
> intended.
>
> Andi
>
>
> -------- Forwarded Message --------
> Subject: Returned post for announce@apache.org
> Date: 4 Jul 2018 21:15:34 -0000
> From: announce-owner@apache.org
> To: kiwiwings@apache.org
>
>
> Hi! This is the ezmlm program. I'm managing the
> announce@apache.org mailing list.
>
> I'm sorry, your message (enclosed) was not accepted by the moderator.
> If the moderator has made any comments, they are shown below.
>
> -------------------- >>>>>
>
> Announcements of Apache project releases must contain a link to the
> relevant
> download page, which might be hosted on an Apache site or a third party
> site
> such as github.com. [1]
>
> The download page must provide public download links where current official
> source releases and accompanying cryptographic files may be obtained. [2]
>
> Links to the download artifacts must support downloads from mirrors. Links
> to
> metadata (SHA, ASC) must be from https://www.apache.org/dist/<p
> roject>/<release>
> MD5 is no longer considered useful and should not be used. SHA is required.
> Links to KEYS must be from https://www.apache.org/dist/<project>/ not
> release
> specific.
>
> Announcements that contain a link to the dyn/closer page alone will be
> rejected by the moderators.
>
> Announcements that contain a link to a web page that does not include a
> link
> to a mirror to the artifact plus links to the signature and at least one
> sha
> checksum will be rejected.
>
> Announcements that link to dist.apache.org will not be accepted.
> Likewise ones which link to SVN or Git code repos.
>
> [1] http://www.apache.org/legal/release-policy.html#release-announcements
> [2] https://www.apache.org/dev/release-distribution#download-links
>
> <<<<< -------------------- <<<<<
>
>
>