+1 to delaying the freeze to get this feature fully in place, especially
since 1.8 will be an LTS release. Is there precedent to doing a freeze with
an exemption for an in progress feature? If so, that is another option to
an outright extension.
Regards,
Michael Manfre
On Sat, Jan 3, 2015 at 8:44
If getting proper support for other template backends would only delay the
1.8 release timeline by a couple weeks, I think that is preferable to a
generalized 1.8 backend which only include DTL until 1.9.
What do others think?
On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin <
aymeric.augus...@p
Hello,
Here’s the thirteenth update (good thing I learnt all these ordinals when I was
a kid!)
https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04
At this point my main concern is the 1.8 feature freeze scheduled in one week.
Dealing properly with some of the items I listed in m
Thank you, Tim, for shepherding this.
On Jan 3, 2015 8:09 AM, "Tim Graham" wrote:
> Here is the fourth update with a week to go until alpha. At this time, I
> am thinking we'll have the feature freeze on Monday, January 12 as planned,
> but perhaps issue the actual alpha release a couple days lat
This week I focused on release blockers and helping with review of the
Model._meta pull request. Thanks to James Bennett for helping me with the
bug fix releases last night.
Report for week ending January 2, 2015:
Triaged
---
https://code.djangoproject.com/ticket/24062 - Reversing Model
Here is the fourth update with a week to go until alpha. At this time, I am
thinking we'll have the feature freeze on Monday, January 12 as planned,
but perhaps issue the actual alpha release a couple days later just to give
some time for some extra polish in case any large patches are committed
