On Saturday, February 7, 2015 at 10:19:24 PM UTC-8, RjOllos wrote: > > Trac has a number of required and optional dependencies across all its > modules. I've attempted to compile a complete list: > http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.4 > > The issue of which versions we support has come up in the following case - > Subversion 1.6 is no longer supported (1) and I'm considering implementing > a change that would be supported in Subversion 1.7, but not in 1.6 (2). It > would be great if we could drop support for Subversion 1.6 in Trac 1.2, but > I feel there should be a formal process for approaching this. > > In some cases we have not been explicit (as far as I know) about what > versions of the dependencies we support. A good place to start would be to > have an informal list of platforms that we are aiming to support. We can > then use that list to decide which versions of the dependencies we'll aim > to support. For example, although Subversion 1.6 is now unsupported by the > Subversion developers, we would want to continue to support it if it was > provided by the official package manager of one the versions of the > platforms we are aiming to support. > > The list of platforms I came up with is: Ubuntu, Debian, Red Hat / CentOS, > Fedora, Suse / OpenSuse, FreeBSD, Windows, Windows Server, Mac OSX. > > What are people using that I overlooked? It might be a good question to > raise in a dedicated thread on trac-users. >
I've forked this discussion since the original thread could get rather lengthy. I prepared the following to post to trac-users, and hoping to get some input on improving the questions before posting it there. Does anyone anticipate that we'll get useful info this way? Is there a better way? --- Recent discussion on the trac-dev (1) mailing list has focused on trying to determine which dependencies we need to support, by considering the most common platforms that Trac runs on. I'm hoping to get some data that is an extension of what we see on TracUsers (2). If you would be so kind as to answer the following questions: 1. Which Trac version are you running? 2. Which OS and what version of the OS are you running? 3. Do you run your own server, use shared hosting (e.g. a VM through a hosting provider) or use an instance of Trac managed by a hosting provider from their servers? Please indicate if you are a hosting provider rather than an end-user. 4. Did you install Trac via your OS's package manager, by directly installing from a package or source (e.g. pip, easy_install, exe or msi installer or direct checkout) or are you running from a prepared image (e.g. Bitnami installer or VM)? 5. If you are running an older version of Trac, are you limited by the version provided by your OS package manager, by a dependency that is not supported in a newer version of Trac (e.g. Python 2.4) or by what is provided by your hosting company? 6. If you are running an older version of an OS, what are the obstacles to upgrading? (1) https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/rg1rsArDIewJ (2) http://trac.edgewall.org/wiki/TracUsers > In general I think it's sufficient to say that we will aim to support the > most recent LTS release with each major release of Trac, provided the LTS > release has been out for a while, say 6 months. I'm most familiar with > Ubuntu and Debian, so I would say that we should aim to support Ubuntu > 14.04 and Debian 7 with the 1.2 release of Trac. > > What I have in mind is to compile a list of platforms we support, and then > list the versions of the dependencies provided by the platforms. From that > we can generate the table of supported dependencies. If this seems like a > good plan, I'm hoping that those familiar with the platforms can help > generate the list. > > Another motivation is, it's burdensome to fix issues associated with old > packages. If we don't state that, for example, Pygments < 1.0 is > unsupported (1.0 was released in 2008) and someone finds an issue with 0.6, > then in my mind we are obligated to fix the issue. Even if Trac will work > with a 5 year old dependency, it would be better to just head off potential > issues and enforce a requirement in the codebase, or at least specify it in > the documentation. > > Thank you for any input on the issue! > > - Ryan > > > (1) > https://subversion.apache.org/docs/release-notes/1.8.html#svn-1.6-deprecation > (2) http://trac.edgewall.org/ticket/11703#comment:5 > > > -- 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.
