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
start.)

Whatever we decide to do, we should update the release guide.

On Tue, Jun 19, 2018 at 2:22 PM Thomas Weise <[email protected]> wrote:

> 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 <[email protected]>
> wrote:
>
>> 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 release
>>
>> Added:
>>     release/beam/2.3.0/
>>     release/beam/2.3.0/apache-beam-2.3.0-python.zip   (with props)
>>     release/beam/2.3.0/apache-beam-2.3.0-python.zip.asc
>>     release/beam/2.3.0/apache-beam-2.3.0-python.zip.md5
>>     release/beam/2.3.0/apache-beam-2.3.0-python.zip.sha1
>>     release/beam/2.3.0/apache-beam-2.3.0-source-release.zip   (with props)
>>     release/beam/2.3.0/apache-beam-2.3.0-source-release.zip.asc
>>     release/beam/2.3.0/apache-beam-2.3.0-source-release.zip.md5
>>     release/beam/2.3.0/apache-beam-2.3.0-source-release.zip.sha1
>>     release/beam/latest   (with props)
>> Removed:
>>     release/beam/0.1.0-incubating/
>>     release/beam/0.2.0-incubating/
>>     release/beam/0.3.0-incubating/
>>     release/beam/0.4.0/
>>     release/beam/0.5.0/
>>     release/beam/0.6.0/
>>     release/beam/2.0.0/
>>     release/beam/2.1.0/
>>     release/beam/2.1.1/
>>     release/beam/2.2.0/
>>
>>
>> I don't think this is the intended release process -- don't we want them
>> up forever?
>>
>> Suggest partial revert of that SVN commit to restore the old releases.
>>
>> On Tue, Jun 19, 2018 at 1:39 PM Chamikara Jayalath <[email protected]>
>> wrote:
>>
>>> 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
>>>
>>
>

Reply via email to