Hmm, the list of blockers seems to be empty. Seeing as its been a while 
since the last update here, any news on a rc/stable release?

On Sunday, December 30, 2012 1:19:04 AM UTC, Russell Keith-Magee wrote:
>
>
> On Sat, Dec 29, 2012 at 2:44 PM, Aidan Zhakypov 
> <aida...@gmail.com<javascript:>
> > wrote:
>
>> Does anyone know when Django 1.5 is going to be released as a stable 
>> version? If I want to *start* developing a production web site, should I 
>> write it on Django 1.4 or is it already ok to implement it on Django 1.5?
>
>
> It's difficult to give an exact date for the release of Django 1.5. We've 
> put out 2 beta releases, which means there are no more features to be 
> added; and the list of release blocking bugs is down to single figures [1]. 
>
> If I were to guess, I'd say we're less than a month from the final release 
> of 1.5. However, this is all dependent on how many new release blocking 
> bugs are discovered between now and then, and the resources that the 
> community and the core team can devote to getting the release out the door.
>
> Whether that suits your own development schedule is up to you. 
>
> The good news is that unless you're planning to use a new feature from 1.5 
> (e.g., pluggable User models), it shouldn't really matter whether you start 
> developing using Django 1.4 or Django 1.5. Django has a strict backwards 
> compatibility policy, so the migration process from 1.4 to 1.5 should be 
> very smooth.
>
> [1] 
> https://code.djangoproject.com/query?status=assigned&status=new&status=reopened&severity=Release+blocker
>
> Yours,
> Russ Magee %-)
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to