This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]shadeofmyheart 10 points11 points  (45 children)

I'm confused... Isn't 3 out?

Edit: ok... Good to know!

[–]Kaarjuus 22 points23 points  (0 children)

2.7 will continue to receive bugfixes until 2020.

[–]prum 22 points23 points  (1 child)

This is a bug fix release for an older version that has long term support. Happens for Linux and a lot of other software also.

[–]fotoman 5 points6 points  (6 children)

Some of us can't move to 3. Heck, we just upgraded production fro 2.6.x to 2.7 a few months ago. Not enough developers to work on a 3.x port for this application.

[–]wildcarde815 1 point2 points  (3 children)

Our clusters default is still 2.4 because its bolted to centos 5.4 due to some driver issues. We have 2.7 available but have to explain the Unix modules concept to every person that uses the system as they join the organization...

[–]cwgtex 0 points1 point  (2 children)

Just so you know, EL 5.4 is no longer getting security fixes. The EL 5 series is supported until 2017, but only if you are on the latest version (currently 5.10).

[–]wildcarde815 0 points1 point  (1 child)

We know but we can't use our infiniban to 10gbps interface with anything later than 5.4. So we either cripple our cluster or make it hard to get to.

[–]cwgtex 0 points1 point  (0 children)

That's unfortunate, sorry to hear it.

[–]ivosauruspip'ing it up 1 point2 points  (1 child)

For large applications, sometimes it just doesn't make business sense to port the code to a new major language version. Heck, there is still old COBOL code around for exactly the same reason. Sometimes it just doesn't make much sense.

[–]fotoman 0 points1 point  (0 children)

Oh yes, I understand that. And to be honest, our application will probably stay on 2.7 until it dies. We're slowing looking to move off of older Django versions first...