Re: 1.9 release planning

2015-06-11 Thread Matt Austin
On 11 June 2015 at 01:37, Collin Anderson wrote: > > I'd propose something slightly different, that's very close to our current > deprecation timeline: > 1.8 (LTS): No features dropped. > 1.9: Dropped features deprecated in 1.5, 1.6, 1.7 > 2.0: Dropped features deprecated in 1.8 > 2.1 (LTS): No fe

Re: Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Matt Austin
Hi Aymeric, On 12 September 2013 18:16, Aymeric Augustin wrote: > Can you confirm that your project has the USE_TZ setting set to True? Yes, USE_TZ is True, pytz is installed, and default timezone is set to UTC. > I believe I introduced it with a patch that made the date lookups (__year, > __

Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Matt Austin
I discovered today that unless timezone data is loaded in to mysql, then previously working (although functionally broken) week_day lookups return an empty queryset. I couldn't find notes in the docs (release notes or queryset week_day docs) that mention this requirement - but happened to read the

Github tags

2012-10-28 Thread Matt Austin
Hi, Would it be possible to get tags for 1.3.3, 1.3.4, 1.4.2, and 1.5 alpha tagged on the github repository? The tagging seems to have fallen behind with these releases. Thanks, -- Matt -- You received this message because you are subscribed to the Google Groups "Django developers" group. To