Re: site doc cleanup

[Andrew Wang <an...@cloudera.com.INVALID>]

It seems aggressive to delete docs just because a line hasn't had a recent
release. We don't have a formal EOL policy for release lines, and old
releases (particularly old clients) are still used and old docs linked in
places.

Also, sorry if I missed the original rationale, but what do we gain from
deleting old docs?

On Fri, Jun 29, 2018 at 8:24 AM Owen O'Malley <ow...@gmail.com>
wrote:

> If propose keeping the last patch release on each X.Y branch and only keep
> the versions that have been being maintained (a patch release in the last
> year?) recently.
>
> Thoughts?
>
> .. Owen
>
> > On Jun 28, 2018, at 19:19, Steve Loughran <st...@hortonworks.com>
> wrote:
> >
> > Rm'd all of 3.0.0-* ; left the current/stable symlinks alone
> >
> > On 27 Jun 2018, at 21:17, Sean Busbey <busbey@cloudera.com<mailto:
> busbey@cloudera.com>> wrote:
> >
> >
> > 3.1.0 was labeled "not ready for production" in its release notes[1].
> > Seems that means 3.0.3 is the stable3 release?
> >
> > Speaking with my HBase hat on I'd rather "current" from the sitemap
> > point at a version folks could reasonably expect HBase to run on top
> > of. Unfortunately, I think that would likely be 2.9.1 due to ongoing
> > issues[2].
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>