On Mon, Feb 9, 2015 at 9:40 AM, Greg Troxel <g...@ir.bbn.com> wrote:

>
> Jun Omae <jun6...@gmail.com> writes:
>
> > I mean it that disagree against dropping support for SVN 1.6 in Trac
> 1.2.x.
> >
> > Hummm, I would agree dropping SVN 1.6 if it means that Trac 1.2.x is
> > likely to work with SVN 1.6, but the version is not officially
> > supported.
>
> I still am having trouble understanding the thought process here.  Why
> do people think it's ok to stay with old subversion but not to stay with
> old trac (1.0.x)?


I am with you on that.

It still potentially hurts us if we can't make incompatible changes with
SVN 1.6.

I don't agree with having Trac held back so that users running old versions
of Red Hat can run the latest version of Trac. Those users can run an old
version of Trac, after all they are running an old version of SVN, so they
are apparently okay with not having the latest and greatest of everything.
If they don't want to run an old version of Trac they can upgrade their OS.
Everything has a cost, and going out of our way to support old platforms
will slow the project. That's why I was hoping we could adopt a rule, such
as supporting the latest version from a set of informally supported OS's
available at the time of a major release. That would imply we should target
RHEL7/CentOS7 with the next major release, 1.2.

Assuming we do try to maintain compatibility with RHEL6/CentOS6, I was even
more concerned that we'd have to continue supporting Python 2.6 for the
next several years due to RHEL6/CentOS6. It appears at least they provide
Python 2.7:
http://rpmfind.net/linux/rpm2html/search.php?query=python&submit=Search+...&system=&arch=

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to