+1 to removing pre-2.x releases from the page
On Wed, Jun 20, 2018 at 12:24 PM Lukasz Cwik wrote:
> Removing the pre-2.x releases sounds like a good idea.
>
> On Wed, Jun 20, 2018 at 11:52 AM Thomas Weise wrote:
>
>> As a related question, what are the thoughts on removing pre 2.x releases
>>
Removing the pre-2.x releases sounds like a good idea.
On Wed, Jun 20, 2018 at 11:52 AM Thomas Weise wrote:
> As a related question, what are the thoughts on removing pre 2.x releases
> from that page?
>
>
> On Wed, Jun 20, 2018 at 6:16 PM, Chamikara Jayalath
> wrote:
>
>> We can also just
As a related question, what are the thoughts on removing pre 2.x releases
from that page?
On Wed, Jun 20, 2018 at 6:16 PM, Chamikara Jayalath
wrote:
> We can also just link to https://beam.apache.org/get-started/downloads/
> and ask users to download the corresponding/latest release.
>
>
> On
We can also just link to https://beam.apache.org/get-started/downloads/ and
ask users to download the corresponding/latest release.
On Wed, Jun 20, 2018 at 9:13 AM Robert Bradshaw wrote:
> So when we send out announcements, etc. we should be linking to
> archive.apache.org so as not to break
So when we send out announcements, etc. we should be linking to
archive.apache.org so as not to break them in the future then. I
suppose we could add another manual step to change the links for old
releases on the website when we do new releases (though the less work
to give the release manager
No, that's not the same storage area. So, latest release is on
dist.apache.org (faster) and previous releases on archive.apache.org.
Regards
JB
On 19/06/2018 23:25, Robert Bradshaw wrote:
> In that case, should we always be linking to the archive? Or is it
> standard practice to change your
That's normal: dist.apache.org should contain only the latest release.
The previous releases are automatically available on archive.apache.org.
So, the website should use archive.apache.org for old release instead of
dist.apache.org.
Regards
JB
On 19/06/2018 23:12, Dan Halperin wrote:
> Looks
Thanks. Sent https://github.com/apache/beam-site/pull/473 fixing currently
broken links.
- Cham
On Tue, Jun 19, 2018 at 2:26 PM Robert Bradshaw wrote:
> In that case, should we always be linking to the archive? Or is it
> standard practice to change your links when things get archived? (You
>
In that case, should we always be linking to the archive? Or is it standard
practice to change your links when things get archived? (You can't, of
course, change links to announcement emails and it's hard to hunt down all
blog posts, etc. so I'd much rather have stable release pointers from the
It is expected that old releases are removed and archived:
http://www.apache.org/legal/release-policy.html#when-to-archive
Old releases are available from http://archive.apache.org/dist/beam/
On Tue, Jun 19, 2018 at 11:12 PM, Dan Halperin wrote:
> Looks like JB removed these during release of
Looks like JB removed these during release of 2.3.0:
svn commit: r25111 - in /release/beam: ./ 0.1.0-incubating/
0.2.0-incubating/ 0.3.0-incubating/ 0.4.0/ 0.5.0/ 0.6.0/ 2.0.0/ 2.1.0/
2.1.1/ 2.2.0/ 2.3.0/
Author: jbonofre
Date: Sat Feb 17 06:08:19 2018
New Revision: 25111
Log:
Publish 2.3.0
I think we want to get the links from https://archive.apache.org/dist/beam/
On Tue, Jun 19, 2018 at 1:39 PM Chamikara Jayalath
wrote:
> I noticed that links to source code of releases is broken in the following
> page for everything but the latest release.
>
>
I noticed that links to source code of releases is broken in the following
page for everything but the latest release.
https://beam.apache.org/get-started/downloads/
For example
http://www-eu.apache.org/dist/beam/2.3.0/apache-beam-2.3.0-source-release.zip
Anybody know how to fix this ?
- Cham
13 matches
Mail list logo
