Ah, thanks Jacob. Also, great job on the 1.5.1 release. Thanks to everyone
for all the hard work.
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 rege
On Thu, Mar 28, 2013 at 2:46 PM, Yo-Yo Ma wrote:
> Will bugs like that one I mentioned in the OP actually be eventually fixed
> in 1.5.1, instead?
No, it's not a critical fix, so the fix'll be in 1.6.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django d
@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
On Thu, Mar 28, 2013 at 1:34 PM, Yo-Yo Ma wrote:
> The commit
> https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3
> fixed 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
>
See https://docs.djangoproject.com/en/dev/internals/git/#other-branches
and also
https://docs.djangoproject.com/en/dev/internals/release-process/#bug-fix-releases
The short version is that stable/* branches only receive "critical"
backports: security fixes, crashers/data-loss bugs, and occasional
The commit
https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3
fixed 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, th
