On Fri, Nov 1, 2019 at 11:35 AM Nathan Hartman <hartman.nathan_at_gmail.com>
wrote:
> On Fri, Nov 1, 2019 at 7:49 AM Julian Foad <julianfoad_at_apache.org> wrote:
> > I found a nice graphic display of Python version lifetimes:
> > "Python Release Cycle" <https://python-release-cycle.glitch.me/>
>
> This graphic is a good resource! (Aside: as part of our website
> reboot, maybe we would like to have a similar graphic for Subversion
> release and support cycles? A picture is worth 1000 words!)
>
> In terms of which Py 3.x version we ultimately choose as the minimum
> supported one going forward, we should decide sooner rather than later.
> We should give everyone the earliest possible heads up in the form of a
> "news" item on the site (and possibly an announcement email???), both
> to let everyone know that 1.14-LTS will support Py 3.x+ and to state
> that with Py 2 EOL, Py 2.7 and <3.x support will be phased out over the
> next few releases.
>
> Mark Phippard wrote:
> > We will still have to support RHEL 7 for a while
>
> Mark: How long (if known) is "a while"? Thanks...
>
>
Note by "we" I meant CollabNet in our products. We will probably support
it for its entire lifespan but maybe when there is a RHEL9 available we
will drop it. We currently still support RHEL 6 too. We do not support
RHEL 8 yet, largely due to this Python 3 issue.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2019-11-01 16:56:16 CET