Removing some old pre-release doco

[Paul King <pa...@asert.com.au>]

Hi folks,

I was thinking of removing some old versions of the doco. It isn't
that disk space is particularly tight but I think it is just easier
for folks to find versions they are after with less clutter from the
noisy pre-release versions. I was thinking of getting rid of:

'2.5.0-rc-1', '2.5.0-rc-2', '2.5.0-rc-3' (we'd be left with 2.5.0
through 2.5.18)

'3.0.0-alpha-1', '3.0.0-alpha-2', '3.0.0-alpha-3', '3.0.0-alpha-4',
'3.0.0-beta-1', '3.0.0-beta-2', '3.0.0-beta-3' (we'd be left with the
RCs and 3.0.0 thru 3.0.12)

'4.0.0-alpha-1', '4.0.0-alpha-2', '4.0.0-alpha-3' (we'd be left with
the betas, RCs and 4.0.0 - 4.0.4)

This wouldn't impact any actual releases (including doc zips) which
would all remain, just the online versions of the docs for those
pre-release versions. Changelogs or versions in Jira would also not be
touched.

Any objections?

Thanks, Paul.

Re: Removing some old pre-release doco

[Paul King <pa...@asert.com.au>]

Okay, I deleted the mentioned versions and the other RC versions for
2.5 & 3 and the beta values for 3 & 4.

I haven't set up any forwarding yet so I have left all versions from
.0s onwards. I know there are projects which link their
javadoc/groovydoc references back to our online versions. They would
break if we don't have forwarding in place. Also, there were probably
a few historic changes which didn't fully comply with semantic
versioning or where we removed long deprecated classes but not on a .0
boundary. They would be rare but would potentially cause the
forwarding scheme to fail. We could craft some kind of crawler to
double check that scenario if we get to the point of being ready to
turn on forwarding. It probably won't make it to the top of my todo
list any time soon but I'm happy to assist with anyone else who feels
inclined to look into it.

Cheers, Paul.

On Mon, Jul 25, 2022 at 1:56 AM Jochen Theodorou <bl...@gmx.org> wrote:
>
> +1.. of course a nice touch would be to make autoforward any link to the
> docu in for example 2.5.0-rc-3 to 2.5.18 (I actually think we do not
> need to keep 2.5.0 - 2.5.17 either). Why the forwarding? To keep
> potential links valid.
>
> bye Jochen
>
>
> On 24.07.22 13:45, Paul King wrote:
> > Hi folks,
> >
> > I was thinking of removing some old versions of the doco. It isn't
> > that disk space is particularly tight but I think it is just easier
> > for folks to find versions they are after with less clutter from the
> > noisy pre-release versions. I was thinking of getting rid of:
> >
> > '2.5.0-rc-1', '2.5.0-rc-2', '2.5.0-rc-3' (we'd be left with 2.5.0
> > through 2.5.18)
> >
> > '3.0.0-alpha-1', '3.0.0-alpha-2', '3.0.0-alpha-3', '3.0.0-alpha-4',
> > '3.0.0-beta-1', '3.0.0-beta-2', '3.0.0-beta-3' (we'd be left with the
> > RCs and 3.0.0 thru 3.0.12)
> >
> > '4.0.0-alpha-1', '4.0.0-alpha-2', '4.0.0-alpha-3' (we'd be left with
> > the betas, RCs and 4.0.0 - 4.0.4)
> >
> > This wouldn't impact any actual releases (including doc zips) which
> > would all remain, just the online versions of the docs for those
> > pre-release versions. Changelogs or versions in Jira would also not be
> > touched.
> >
> > Any objections?
> >
> > Thanks, Paul.
>

Re: Removing some old pre-release doco

[Jochen Theodorou <bl...@gmx.org>]

+1.. of course a nice touch would be to make autoforward any link to the
docu in for example 2.5.0-rc-3 to 2.5.18 (I actually think we do not
need to keep 2.5.0 - 2.5.17 either). Why the forwarding? To keep
potential links valid.

bye Jochen


On 24.07.22 13:45, Paul King wrote:
> Hi folks,
>
> I was thinking of removing some old versions of the doco. It isn't
> that disk space is particularly tight but I think it is just easier
> for folks to find versions they are after with less clutter from the
> noisy pre-release versions. I was thinking of getting rid of:
>
> '2.5.0-rc-1', '2.5.0-rc-2', '2.5.0-rc-3' (we'd be left with 2.5.0
> through 2.5.18)
>
> '3.0.0-alpha-1', '3.0.0-alpha-2', '3.0.0-alpha-3', '3.0.0-alpha-4',
> '3.0.0-beta-1', '3.0.0-beta-2', '3.0.0-beta-3' (we'd be left with the
> RCs and 3.0.0 thru 3.0.12)
>
> '4.0.0-alpha-1', '4.0.0-alpha-2', '4.0.0-alpha-3' (we'd be left with
> the betas, RCs and 4.0.0 - 4.0.4)
>
> This wouldn't impact any actual releases (including doc zips) which
> would all remain, just the online versions of the docs for those
> pre-release versions. Changelogs or versions in Jira would also not be
> touched.
>
> Any objections?
>
> Thanks, Paul.

Re: Removing some old pre-release doco

[Andres Almiray <aa...@gmail.com>]

+1

I think this is the sensible thing to do. 

Sent from my primitive tricorder

> On 24 Jul 2022, at 13:45, Paul King <pa...@asert.com.au> wrote:
> 
> Hi folks,
> 
> I was thinking of removing some old versions of the doco. It isn't
> that disk space is particularly tight but I think it is just easier
> for folks to find versions they are after with less clutter from the
> noisy pre-release versions. I was thinking of getting rid of:
> 
> '2.5.0-rc-1', '2.5.0-rc-2', '2.5.0-rc-3' (we'd be left with 2.5.0
> through 2.5.18)
> 
> '3.0.0-alpha-1', '3.0.0-alpha-2', '3.0.0-alpha-3', '3.0.0-alpha-4',
> '3.0.0-beta-1', '3.0.0-beta-2', '3.0.0-beta-3' (we'd be left with the
> RCs and 3.0.0 thru 3.0.12)
> 
> '4.0.0-alpha-1', '4.0.0-alpha-2', '4.0.0-alpha-3' (we'd be left with
> the betas, RCs and 4.0.0 - 4.0.4)
> 
> This wouldn't impact any actual releases (including doc zips) which
> would all remain, just the online versions of the docs for those
> pre-release versions. Changelogs or versions in Jira would also not be
> touched.
> 
> Any objections?
> 
> Thanks, Paul.