Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: <B32E24FC-D87A-4941-9984-9AA308CCC7E0@apache.org>
References: <CAKiyyaHREZwtx4d1iC9j+vgf=8pfPE5Bte5quWnGGMERqF0Fvg@mail.gmail.com>
 <3FCABB07-E692-4CCE-9E46-148987B05630@data-artisans.com> <CALte62wTiymO4VH5yFN-6aDzMQyAXeSEkFz2Dex9ExTMZsK2xw@mail.gmail.com>
 <CAKiyyaHakgU67PgE7Ym8VRQmYGF91qsHHtvcupGQx8R2adhZDQ@mail.gmail.com>
 <CAKiyyaEo6z0ztrdK66nS7P_c1SJHzhmtYoV67ym-XbHjkZ1aSw@mail.gmail.com>
 <CANC1h_sKiN46b+vE_x7RgL8hodaPri44fKwrEG02qgV6L3yDPg@mail.gmail.com> <B32E24FC-D87A-4941-9984-9AA308CCC7E0@apache.org>
From: Robert Metzger <rmetzger@apache.org>
Date: Tue, 22 Aug 2017 18:07:06 +0200
Message-ID: <CAGr9p8C=cpBTC6VsPcrvF=fmWgoKmZhueh2S5EwynontCf5YGQ@mail.gmail.com>
Subject: Re: [DISCUSS] Stop serving docs for Flink version prior to 1.0
To: "dev@flink.apache.org" <dev@flink.apache.org>
Cc: Ufuk Celebi <uce@apache.org>
Content-Type: multipart/alternative; boundary="94eb2c0b8438a6422b055759caf4"

--94eb2c0b8438a6422b055759caf4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Please go ahead +1

Thank you for taking care!

On Tue, Aug 22, 2017 at 6:02 PM, Aljoscha Krettek <aljoscha@apache.org>
wrote:

> +1
> > On 22. Aug 2017, at 18:01, Stephan Ewen <sewen@apache.org> wrote:
> >
> > +1
> >
> > On Tue, Aug 22, 2017 at 5:58 PM, Ufuk Celebi <uce@apache.org> wrote:
> >
> >> Quick update: If there are no objections, I will start looking into
> >> how to stop serving the docs for Flink < 1.0 after tomorrow.
> >>
> >>
> >> On Wed, Aug 16, 2017 at 10:45 PM, Ufuk Celebi <uce@apache.org> wrote:
> >>> Thanks for your early feedback Kostas and Ted.
> >>>
> >>> @Kostas: I have a proposal for a more obvious warning here:
> >>> https://github.com/apache/flink/pull/4553 Would appreciate comments i=
n
> >>> that PR too :-)
> >>>
> >>>
> >>> On Wed, Aug 16, 2017 at 6:56 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >>>> Without any upgrade path, the old versions are not useful.
> >>>>
> >>>> +1 on redirecting doc to stable release(s).
> >>>>
> >>>> On Wed, Aug 16, 2017 at 9:46 AM, Kostas Kloudas <
> >> k.kloudas@data-artisans.com
> >>>>> wrote:
> >>>>
> >>>>> Hi Ufuk,
> >>>>>
> >>>>> +1
> >>>>>
> >>>>> I think that this is a nice change!
> >>>>> Thanks Ufuk for opening the discussion.
> >>>>>
> >>>>> I think that broken/redirect links are not an issue,
> >>>>> as either way the information provided is far outdated
> >>>>> (=3D=3D wrong).
> >>>>>
> >>>>> As for the warning, we cannot put it in the header instead
> >>>>> of the footer? Sth like, this page may contain outdated info,
> >>>>> please refer to XXX for an updated version.
> >>>>>
> >>>>> Kostas
> >>>>>
> >>>>>> On Aug 16, 2017, at 6:02 PM, Ufuk Celebi <uce@apache.org> wrote:
> >>>>>>
> >>>>>> Hey devs,
> >>>>>>
> >>>>>> I would like to stop serving the documentation for all Flink
> versions
> >>>>>> prior to 1.0.
> >>>>>>
> >>>>>> Do you have any concerns about this?
> >>>>>>
> >>>>>> These Flink versions are very old without any upgrade path to newe=
r
> >>>>>> versions but they still get a lot of traffic and most new users
> don't
> >>>>>> realize that they are looking at a very outdated docs page.
> >>>>>>
> >>>>>> Even with a stronger warning about being outdated, I don't see a
> >> point
> >>>>>> in serving them.
> >>>>>>
> >>>>>> If we choose to do this, I would redirect these ancient pages to t=
he
> >>>>>> docs of the latest stable release and update the release process
> Wiki
> >>>>>> page to update those redirects etc.
> >>>>>>
> >>>>>> This will mean that some links in old StackOverflow questions and
> the
> >>>>>> mailing list archives will be broken/redirected. If you have
> concerns
> >>>>>> about this, please raise your voice in this thread.
> >>>>>>
> >>>>>> =E2=80=93 Ufuk
> >>>>>>
> >>>>>> PS: I've created an issue to improve the visibility of the outdate=
d
> >>>>>> warning here https://issues.apache.org/jira/browse/FLINK-7462. I
> >> will
> >>>>>> only apply this to versions >=3D 1.0 for now.
> >>>>>
> >>>>>
> >>
>
>

--94eb2c0b8438a6422b055759caf4--