Are Django versions released too often?
17th December 2013
My answer to Are Django versions released too often? on Quora
The Django release process is well documented (see Django’s release process) and has been specifically designed to address the concerns of developers who don’t want to have to spend too much time keeping up to date with the latest version.
Minor releases happen roughly every nine months, and introduce new features usually without breaking backwards compatibility. If a feature is deprecated, it will raise a warning in the version that deprecates it, a louder warning in the next version (9 months later) and will be removed in the version after that (1.5 years after the feature removal was first announced).
If even that is too fast for you, you can stick with a “Long-term support” release, which get security fixes applied for 3+ years. Django 1.4 is the most recent of these, and will be supported until at least March 2015.
Read https://docs.djangoproject.com/e... for more information. Personally (and I’ve had no input at all in to the release process design) I think it’s all extremely well thought out.
More recent articles
- Weeknotes: the Datasette Cloud API, a podcast appearance and more - 1st October 2023
- Things I've learned about building CLI tools in Python - 30th September 2023
- Talking Large Language Models with Rooftop Ruby - 29th September 2023
- Weeknotes: Embeddings, more embeddings and Datasette Cloud - 17th September 2023
- Build an image search engine with llm-clip, chat with models with llm chat - 12th September 2023
- LLM now provides tools for working with embeddings - 4th September 2023
- Datasette 1.0a4 and 1.0a5, plus weeknotes - 30th August 2023
- Making Large Language Models work for you - 27th August 2023
- Datasette Cloud, Datasette 1.0a3, llm-mlc and more - 16th August 2023
- How I make annotated presentations - 6th August 2023