Hey folks -- One thing about 1.5 that's of particular note to -developers: this marks the beginning of our "master is always open" policy. That is, we're *not* freezing the master branch until 1.5 is released; new features can continue to go into master as soon as they're ready.
This is a pretty big change from the way we used to do it (freeze trunk until after the final), and hopefully this means less bitrot since patches that're ready can go in immediately. So if you've got something that was nearly ready but missed the 1.5 freeze today, you can still get it in any time. It just won't make 1.5, but it *will* be there on master, ready for 1.6. Jacob On Thu, Oct 25, 2012 at 2:58 PM, James Bennett <ubernost...@gmail.com> wrote: > Our first milestone on the road to Django 1.5 came today, with the > release of the first alpha package. > > Blog post about it is here: > > https://www.djangoproject.com/weblog/2012/oct/25/15-alpha-1/ > > Release notes are here: > > https://docs.djangoproject.com/en/dev/releases/1.5-alpha-1/ > > And you can get the alpha from the downloads page: > > https://www.djangoproject.com/download/ > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
