You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Shawn McKinney <sm...@apache.org> on 2018/07/23 22:22:22 UTC

Fwd: Returned post for announce@apache.org

Hello,

Last Saturday my release notice to announce@apache.org <ma...@apache.org> was rejected.  

The 1st reason for the rejection is trivial, having not placed a link to the downloads in the announcement.

The 2nd reason, is fortress' download page has links to dist.apache.org <http://dist.apache.org/>. 

First, I thought this was wrong, because our jars are downloaded via the mirrors.  However, the metadata files (.asc, .md5,…) are indeed pointing to dist.apache.org.

Looking at the other directory subprojects, apacheds, api, studio, I noticed they too have the same problem.

Obviously there are new rules in place for publishing notices about project releases.

So, this is an FYI.  I suspect you’ll run into this on your next release.  

I’m currently looking at the download pages, trying to figure out how to fix this problem and interested in what others think.

Thanks,
— Shawn

> Begin forwarded message:
> 
> From: Private LIst Moderation <mo...@gsuite.cloud.apache.org>
> Subject: Re: Returned post for announce@apache.org
> Date: July 21, 2018 at 7:06:58 PM CDT
> To: Shawn McKinney <sm...@apache.org>
> Cc: announce-owner@apache.org
> 
> Two problems with the announcement. These are explicitly called out in the reject message.
> 
> 1. There is no link in the announcement to the download page. This is minor and can be fixed simply by adding the link to the download page.
> 
> 2. The links on the download page to metadata files e.g.
> https://dist.apache.org/repos/dist/release/directory/fortress/dist/2.0.1/fortress-core-2.0.1.jar.asc
> must not refer to dist.apache.org.
> 
> Please resubmit the announcement after fixing the above.
> 
> Hope this helps.
> 
> Craig
> 
>> On Jul 21, 2018, at 3:21 PM, Shawn McKinney <sm...@apache.org> wrote:
>> 
>> 
>>> On Jul 21, 2018, at 3:10 PM, announce-owner@apache.org wrote:
>>> 
>>> 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.
>> 
>> Confused by this.  The announcement has a link to apache fortress project page which points to downloads, that have the req’s artifacts / signatures.  Please explain.
>> 
>> Thanks
>> —Shawn
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>

Re: Returned post for announce@apache.org

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 07/24/2018 05:38 PM, Shawn McKinney wrote:
> 
>> On Jul 24, 2018, at 12:26 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> Best look at the LDAP API download pages, those was recently updated to
>> the new rules. See also the Jira that Emmanuel created [1]. And also
>> remove the md5.
>>
>> Kind Regards,
>> Stefan
>>
>> [1] https://issues.apache.org/jira/browse/DIR-330
> 
> Ah I missed that JIRA. 
> 
> One more point of confusion.  The links our metadata tags use should point to:
> 
> https://www.apache.org/dist/directory/…
> 
> not
> 
> https://dist.apache.org/repos/dist/release/directory/…
> 
> Is that correct?

Yes, but we upload them to dist.apache.org/repos/dist/release/directory,
from there they are magically (r)synced to www.apache.org/dist/directory.

Kind Regards,
Stefan

Re: Returned post for announce@apache.org

Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 24, 2018, at 12:26 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
> 
> Best look at the LDAP API download pages, those was recently updated to
> the new rules. See also the Jira that Emmanuel created [1]. And also
> remove the md5.
> 
> Kind Regards,
> Stefan
> 
> [1] https://issues.apache.org/jira/browse/DIR-330

Ah I missed that JIRA. 

One more point of confusion.  The links our metadata tags use should point to:

https://www.apache.org/dist/directory/…

not

https://dist.apache.org/repos/dist/release/directory/…

Is that correct?

Thanks,
—Shawn

Re: Fwd: Returned post for announce@apache.org

Posted by Emmanuel Lecharny <el...@apache.org>.
We have to review all the projects and update their respective dev guide.
It’s on my agenda when I’ll be back from vacations (tonite).

Le mar. 24 juil. 2018 à 07:26, Stefan Seelmann <ma...@stefan-seelmann.de> a
écrit :

> On 07/24/2018 12:22 AM, Shawn McKinney wrote:
> > Hello,
> >
> > Last Saturday my release notice to announce@apache.org <mailto:
> announce@apache.org> was rejected.
> >
> > The 1st reason for the rejection is trivial, having not placed a link to
> the downloads in the announcement.
> >
> > The 2nd reason, is fortress' download page has links to dist.apache.org
> <http://dist.apache.org/>.
> >
> > First, I thought this was wrong, because our jars are downloaded via the
> mirrors.  However, the metadata files (.asc, .md5,…) are indeed pointing to
> dist.apache.org.
> >
> > Looking at the other directory subprojects, apacheds, api, studio, I
> noticed they too have the same problem.
> >
> > Obviously there are new rules in place for publishing notices about
> project releases.
> >
> > So, this is an FYI.  I suspect you’ll run into this on your next
> release.
> >
> > I’m currently looking at the download pages, trying to figure out how to
> fix this problem and interested in what others think.
>
> Thanks for the info, Shawn.
>
> Best look at the LDAP API download pages, those was recently updated to
> the new rules. See also the Jira that Emmanuel created [1]. And also
> remove the md5.
>
> Kind Regards,
> Stefan
>
> [1] https://issues.apache.org/jira/browse/DIR-330
>
-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Fwd: Returned post for announce@apache.org

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 07/24/2018 12:22 AM, Shawn McKinney wrote:
> Hello,
> 
> Last Saturday my release notice to announce@apache.org <ma...@apache.org> was rejected.  
> 
> The 1st reason for the rejection is trivial, having not placed a link to the downloads in the announcement.
> 
> The 2nd reason, is fortress' download page has links to dist.apache.org <http://dist.apache.org/>. 
> 
> First, I thought this was wrong, because our jars are downloaded via the mirrors.  However, the metadata files (.asc, .md5,…) are indeed pointing to dist.apache.org.
> 
> Looking at the other directory subprojects, apacheds, api, studio, I noticed they too have the same problem.
> 
> Obviously there are new rules in place for publishing notices about project releases.
> 
> So, this is an FYI.  I suspect you’ll run into this on your next release.  
> 
> I’m currently looking at the download pages, trying to figure out how to fix this problem and interested in what others think.

Thanks for the info, Shawn.

Best look at the LDAP API download pages, those was recently updated to
the new rules. See also the Jira that Emmanuel created [1]. And also
remove the md5.

Kind Regards,
Stefan

[1] https://issues.apache.org/jira/browse/DIR-330