The clutch process produces proper release links for all podling releases. That 
could be extended to artifacts in the dev part of dist.

Regards,
Dave

Sent from my iPhone

> On Feb 27, 2020, at 4:37 PM, Craig Russell <apache....@gmail.com> wrote:
> 
> There already is a policy in place that requires projects to have download 
> pages, so podlings will need to create them. [1] [2] 
> 
> We do have an ongoing request for the binary artifact policy to be clarified.
> 
> There are over 200 download pages that can be used to get an idea of what is 
> expected. 
> 
> The biggest issue that I see is that prior to making a download page work, 
> the links behind the page need to be active, and those links are only active 
> after the vote passes, and the artifacts, checksums, and signatures are 
> uploaded.
> 
> So maybe it's too big an ask for the download page(s) to be created earlier 
> for review.
> 
> Craig
> 
> [1] http://www.apache.org/legal/release-policy.html
> [2] https://www.apache.org/dev/release-distribution#download-links
> 
>> On Feb 27, 2020, at 12:17 AM, Ning Wang <wangnin...@gmail.com> wrote:
>> 
>> Interesting. I feel the requirements for binary packages could be more
>> clear. A dedicated download page might be a bit over kill IMHO but some
>> suggestions and examples could be helpful.
>> 
>>> On Wed, Feb 26, 2020 at 9:20 PM Craig Russell <apache....@gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> I guess I'm looking for a way for podlings to get help creating a download
>>> page that is consistent with the requirements, before the announcement is
>>> rejected for not having a good download page.
>>> 
>>> Other suggestions?
>>> 
>>> Craig
>>> 
>>> 
>>>> On Feb 26, 2020, at 6:28 AM, Josh Fischer <j...@joshfischer.io> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I'm not sure I follow.  What value is added by creating the download page
>>>> earlier as opposed to just sending out the direct download link via
>>> email?
>>>> It seems like it could be more work swapping out those artifact URLs in
>>>> the release download page in the beginning. If the release candidate
>>> didn't
>>>> pass it's just a little more work to be done for the next  RC vote.
>>> I'm
>>>> still learning the ropes here, so I'm most likely just out of the loop.
>>>> 
>>>> - Josh
>>>> 
>>>> On Sun, Feb 23, 2020 at 10:37 PM Craig Russell <apache....@gmail.com>
>>> wrote:
>>>> 
>>>>> Announcements of Apache releases need to follow a specific protocol,
>>> and I
>>>>> wonder if there is some way for folks here to review announcements and
>>>>> download pages of podlings before they get sent out and rejected.
>>>>> https://www.apache.org/dev/release-distribution#download-links
>>>>> 
>>>>> Would it make sense for podlings to create a download page earlier in
>>> the
>>>>> process and have it reviewed as part of a release review?
>>>>> 
>>>>> Craig
>>>>> 
>>>>> Craig L Russell
>>>>> c...@apache.org
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>>> 
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> Craig L Russell
> c...@apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to