On 7/1/2010 6:23 PM, Eli Carter wrote:
On Tuesday 29 June 2010 11:55:13 am Noah Kantrowitz wrote:
On Jun 29, 2010, at 12:29 AM, Remy Blank wrote:
Felix Schwarz wrote:
1. Python 2.4 support. RHEL 5 ships 2.4 and is one of the major Linux
distributions out there (especially for shared hosting).
Currently I
have problems installing 0.12 on some production servers as they
are
still running RHEL 4 (Python 2.3!) which will change in 2012.
RHEL 5 will be supported until 2014 and I'd like to make a point
of
supporting it for a couple of years more.
While I understand the idea of stability advertised for RHEL, I
wouldn't
want to bear the cost of supporting such a policy. I mean, we're two
and
a half developers here, and we should be doing the work for a
multi-million dollar company? I don't see that happen. Red Hat is of
course free to provide old patched versions, but I don't want to
restrict our available feature set (and therefore development speed)
for
that.
Also if someone is running RHEL 5 (or 4) then by definition they are
okay with running older software in favor of stability. Assuming RHEL
ships Trac 0.10 or 0.11, that will continue to work forever.
That's not how I see it. Choosing an enterprise distro means not wanting to
have to rebuild your server every year. That's different from not wanting to
use a current version of Trac. I think we should support running Trac on the
latest release of all the major enterprise distros. RHEL/CentOS is the distro
I use; Debian, Ubuntu's LTS, and SUSE Enterprise would also count.
(RHEL/CentOS and Ubuntu LTS are the ones I most often see used.)
0.11 will shortly be unsupported. 0.12 will be unsupported shortly after the
0.13 release (targeted for the end of this year). At that point, no
_supported_ version of Trac will run on RHEL/CentOS.
No, with more frequent recent release cycles, we'll have to support more
than just the immediate previous release line. Furthermore, if anyone
cares to have a Trac version compatible with Python 2.4, for as long as
needed, I don't see a reason why we should "terminate" prematurely the
support for 0.12.
Btw, the same goes for 0.11 today. We said we're going to make the last
release for 0.11.x only because no one has demonstrated a wish to
maintain 0.11 any longer. But the branch can be reopened anytime, if
someone really feels strongly to continue the support for the benefit of
Python 2.3 users.
I still think we need to support the most recent RHEL, and should therefore
retain support for python 2.4. Once RHEL6 comes out, I'll fully support
dropping 2.4 support. Unfortunately, I can find no public schedule for when
it is supposed to come out, though Beta2 is now publicly available.
That said, life has conspired against my Trac development time, and the two
contributors doing most of the work want to move to 2.5 for valid reasons, so
I expect my objection won't change anything. I'm hoping RHEL6 will come out
soon and make the issue moot anyway, but I've been hoping that for a year+
now.
Well, I think you can be reasonably assured that 0.12 will be supported
for more than the next 6 months, say until RHEL6 comes out, for example ;-)
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
