On Fri, Dec 21, 2018 at 4:41 PM sebb wrote:
> ...links to release artifacts must use a URL that starts with
> http://www.apache.org/dyn/closer.cgi/curator/ ...
Or use the form-based mirror selection mechanism like we do at
https://sling.apache.org/downloads.cgi - details earlier in this
thread.
OK - I would now update my spec for a download page to be:
Your Apache Download page...
- ...must have at least one link to the current release. This link must
use the "closer" utility. For example:
https://www.apache.org/dyn/closer.lua/PROJECT/VERSION/SOURCE-RELEASE
- ...m
On Fri, 21 Dec 2018 at 14:58, Jordan Zimmerman
wrote:
>
> I still don't understand whether or not this link "
> http://www.apache.org/dyn/closer.cgi/curator/"; is allowed on the download
> page at all. Sebb's last comment was "yes and no". I have trouble following
> that reply. Clear guidance is n
I still don't understand whether or not this link "
http://www.apache.org/dyn/closer.cgi/curator/"; is allowed on the download
page at all. Sebb's last comment was "yes and no". I have trouble following
that reply. Clear guidance is needed here. Is it allowed or not? Curator
was told no. What I nee
Hi,
On Thu, Dec 20, 2018 at 11:36 PM Jordan Zimmerman wrote:
> ...A template with correct links
> (with simple replacements for project name and version) would be
> very helpful
It's not really a generic template but maybe what Sling is doing
helps, the download page at https://sling.apache.
On 21/12/2018 00:21, Daniel Gruno wrote:
On 12/21/18 1:14 AM, Jordan Zimmerman wrote:
I believe the JClouds download page is _not_ in compliance. Curator was
just told:
Also the page links directly to
http://www.apache.org/dyn/closer.cgi/curator/
This is not allowed.
Why would that not be
On Fri, 21 Dec 2018 at 00:21, Daniel Gruno wrote:
>
> On 12/21/18 1:14 AM, Jordan Zimmerman wrote:
> > I believe the JClouds download page is _not_ in compliance. Curator was
> > just told:
> >
> > Also the page links directly to
> >> http://www.apache.org/dyn/closer.cgi/curator/
> >> This is not
On 12/21/18 1:14 AM, Jordan Zimmerman wrote:
I believe the JClouds download page is _not_ in compliance. Curator was
just told:
Also the page links directly to
http://www.apache.org/dyn/closer.cgi/curator/
This is not allowed.
Why would that not be allowed? That's exactly what we want you to
I believe the JClouds download page is _not_ in compliance. Curator was
just told:
Also the page links directly to
> http://www.apache.org/dyn/closer.cgi/curator/
> This is not allowed.
The JClouds download page has a direct link to the "closer" (
https://www.apache.org/dyn/closer.cgi/jclouds/).
In ORC, we use jekyll to generate the site. One of the advantages is that
we can use templating to make things easier.
We have three states that a release can be in:
* current - the current release artifacts from the mirrors and the
checksums on dist
* stable - the previous minor version, but stil
We had the same issue recently in jclouds. Although I can't speak for the
minimum set of concrete links required, you may find our page useful:
Page: https://jclouds.apache.org/start/install/
Source: https://github.com/jclouds/jclouds-site/blob/master/start/install.md
HTH,
I.
On Thu, Dec 20, 20
Hi Folks,
Maybe it's just me but I've been having a heck of a time getting the Apache
Curator download page to conform to spec. A template with correct links
(with simple replacements for project name and version) would be
very helpful. I've been using other project download pages as a guide but
a
12 matches
Mail list logo
