I did take extra care and I looked on the last release by double checking
it.


What’s wrong?

On Fri, Sep 6, 2019 at 11:47 AM Robbie Gemmell <robbie.gemm...@gmail.com>
wrote:

> As more of an aside, it isnt really necessary to make any of those
> changes and risk getting it wrong like this...just copy the previous
> entry on the past releases page and find+replace the version numbers
> in that with your text editor of choice, done.
>
> On Fri, 6 Sep 2019 at 16:33, Timothy Bish <tabish...@gmail.com> wrote:
> >
> > It would appear that this problem has occurred again.  The past releases
> > page was partially updated but in all cases the updates were incorrect
> and
> > now the download links are broken.  The links to the all broker release
> > archives themselves point to Apache Archives but the action=download bit
> at
> > the end of the URI was not removed.  The links to the checksums and
> > signatures were not updated to point to archives it seems and so those
> are
> > also broken.
> >
> > On Mon, Jun 3, 2019 at 6:44 AM Robbie Gemmell <robbie.gemm...@gmail.com>
> > wrote:
> >
> > > Its more that the download links for the previous release themselves
> > > are broken thats the issue. The docs link is often incorrect too, but
> > > it tends to at least somewhat 'work' when wrong (from pointing to
> > > "latest" rather than the actual versions release docs).
> > >
> > > I think the existing process needed (copy+paste the previous entry in
> > > file, find+replace the version number) is actually fairly easy. Its
> > > just not being followed, and the links also arent being inspected
> > > afterwards to notice that it wasnt.
> > >
> > > Robbie
> > >
> > > On Fri, 31 May 2019 at 17:25, Clebert Suconic <
> clebert.suco...@gmail.com>
> > > wrote:
> > > >
> > > > Please accept my apologies... I have been on so many channels all at
> > > > once that I overlooked into this.
> > > >
> > > > it would be nice to make this simpler though. I have tried to get rid
> > > > of the documentation per previous version for instance (you can just
> > > > download the documentation with the zip).
> > > >
> > > > On Fri, May 31, 2019 at 5:35 AM Robbie Gemmell <
> robbie.gemm...@gmail.com>
> > > wrote:
> > > > >
> > > > > Yes it is, I even noted I found it was already documented when I
> went
> > > > > to add one of the times I was reporting the issue.
> > > > >
> > > > >
> > >
> https://github.com/apache/activemq-artemis/blame/2.8.1/RELEASING.md#L299
> > > > > (The details are a touch stale now in referring to html of the old
> > > > > site update process)
> > > > >
> > > > > On Fri, 31 May 2019 at 10:22, Gary Tully <gary.tu...@gmail.com>
> wrote:
> > > > > >
> > > > > > is that step in:
> > > > > >
> https://github.com/apache/activemq-artemis/blob/master/RELEASING.md
> > > > > >
> > > > > >
> > > > > > On Thu, 30 May 2019 at 12:29, Robbie Gemmell <
> > > robbie.gemm...@gmail.com> wrote:
> > > > > > >
> > > > > > > I've found that the docs/downloads/etc links for recent
> releases on
> > > > > > > the past releases page are broken nearly every time I have
> used the
> > > > > > > page over the last couple of years. I've fixed it a bunch of
> times,
> > > > > > > reported it several times to try and stop it from actually
> > > happening,
> > > > > > > and fixed it some more times as it keeps doing so.
> > > > > > >
> > > > > > > It is difficult to understand how the same issue keeps
> happening
> > > > > > > repeatedly given how trivial the page is to update and how
> > > quick/easy
> > > > > > > it is to verify the links while doing so, e.g by hovering over
> > > them,
> > > > > > > or actually clicking them like a user might and see them 404
> or go
> > > the
> > > > > > > wrong place if the files havent been cleared from the mirroring
> > > area
> > > > > > > just yet.
> > > > > > >
> > > > > > > As the page is proving so troublesome to maintain in working
> > > order, I
> > > > > > > think the per-release content might be better jsut removed and
> only
> > > > > > > the direct link to the archive parent dir left. Thats where I
> will
> > > be
> > > > > > > going directly in future to save myself the hassle (of
> noticing the
> > > > > > > page is broken and feeling I should report it or fix it yet
> again).
> > > > > > >
> > > > > > > Robbie
> > > >
> > > >
> > > >
> > > > --
> > > > Clebert Suconic
> > >
> >
> >
> > --
> > --
> > Tim Bish
>
-- 
Clebert Suconic

Reply via email to