No Django release since March 2007
The most popularly suggested “alternative” to Ruby on Rails, Django, has not seen a full tagged release since March 2007, 0.96. This is pretty, uh, bad - how are you supposed to establish a baseline compatibility for your app? Refer to the subversion number?
I evaluated Django a couple of times 12-18 months ago, but ended up staying with Rails. Now I’m glad I did. There are very good reasons for picking some targets and doing a “release” every so often, and some equally good ones for not simply telling everyone to work out of trunk. There’s no excuse for it - subversion may not be as flexible as Git but tagging a release is simplicity itself. Hell, what is stopping them doing it right now? Even if there’s no good roadmap or release plan, anything is better than nothing. It’s a single command!
I’ve been critical of Rails Core’s professionalism in the past, but Django are making them look like calm, super-organised air traffic controllers compared to “tagged releases? who needs them just check out trunk LOL”.
What a mess.
Tags: django