@Jacob - thank you much. That was the exact docs page I didn't think 
existed.
@Ramiro - I meant using stable/1.5.x in production.

BTW, Jacob, the first of 2 docs links you provided mentioned providing bug 
fixes for the most recent release, and follows up with essentially, 
"they're at stable/A.B.x". Will bugs like that one I mentioned in the OP 
actually be eventually fixed in 1.5.1, instead? I'm just trying to decide 
what the best thing (tag, commit, branch tip, etc.) to install to make sure 
I get those sorts of updates in my production server. It could be just that 
I install the tip of master and test it out before updating, but that's not 
ideal of course.


On Thursday, March 28, 2013 12:34:56 PM UTC-4, Yo-Yo Ma wrote:
>
> The commit 
> https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3fixed
>  a problem where a custom regex validator's customized message was 
> ignored, in favor of the one set on the class (you just see "Please enter a 
> valid value").
>
> If I pip install the latest master, the problem is of course fixed. If I 
> pip install stable/1.5.x, the problem persists.
>
> I searched the docs for info about using the stable/1.x.x branches, but 
> couldn't find anything, so I wanted to ask:
>
> 1) Is doing so considered safe (e.g., for production usage), since they're 
> "stable"?
> 2) What is the policy or lag time for getting commits such as the 
> aforementioned bug-fix into these stable branches?
> 3) Are there docs for this, and if not, should there be an entry on 
> https://docs.djangoproject.com/en/dev/faq/install/?
>
>

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


Reply via email to