On Mon, Feb 9, 2015 at 9:47 AM, Ryan Ollos <rjol...@gmail.com> wrote:
> 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= > > I didn't setup that filter correctly and it appears the info isn't available through that database. From a quick search it appears that RHEL6/CentOS6 may not provide Python 2.7: ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/ http://distrowatch.com/table.php?distribution=redhat Dropping support for Python 2.6 is an issue really worth discussing. Keeping supporting for Python 2.6 indefinitely is something that will really slow us down and make it even harder to get to Python 3.x someday. We have already committed to supporting Python 2.6 in Trac 1.2.x, but I'd like to drop support for Python 2.6 starting with 1.3.1. I'm really tired of testing on multiple versions of Python and worrying about using incompatible features. The situation has gotten better now that we don't develop Trac 0.12.x, which supports Python 2.4, but we still have to worry about Python 2.5 in Trac 1.0.x, and I'm eager to move on. By this time next year it would be ideal if development was focused on 1.3.x and we only had to test against Python 2.7. -- 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.
