Re: status of 1.10 release blockers

2016-09-05 Thread Tim Graham 
As usual, the monthly bug fix release (1.10.1) is planned for tomorrow, 
September 1.

There's one issue that could use some attention. The new migrations history 
consistency checks in makemigrations have triggered some problems in 
various multiple database setups, such as with a read-only non-default 
database. I implemented a proposal to consult database routers to decide 
whether or not to do the checks, however, there remains some possibility of 
backwards-incompatibility as described in 
https://code.djangoproject.com/ticket/27142#comment:11. I don't mind 
deferring the issue until next month if there isn't a consensus. In 
particular, there's been no feedback from the ticket reporters on whether 
or not the PR works for them.

PR: https://github.com/django/django/pull/7194

On Saturday, July 30, 2016 at 9:20:46 PM UTC-4, Tim Graham wrote:
>
> The final release is on schedule for Monday, August 1.
>
> On Thursday, July 14, 2016 at 10:05:39 AM UTC-4, Markus Holtermann wrote:
>>
>> Thank you for the update, Tim. 
>>
>> #26888 will be taken care of by tomorrow. Either Marten or I are pushing 
>> a PR. 
>>
>> Cheers, 
>>
>> /Markus 
>>
>> On Thu, Jul 14, 2016 at 06:41:51AM -0700, Tim Graham wrote: 
>> >I'm planning for the release candidate on Monday. 
>> > 
>> >The one blocker is #26888  
>> - 
>> >RegexURLResolver doesn't work in threaded environments. 
>> > 
>> >On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote: 
>> >> 
>> >> The blocker is merged so I'll release the beta in a couple hours if no 
>> one 
>> >> stops me. 
>> >> 
>> >> On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote: 
>> >>> 
>> >>> The remaining blocker: 
>> >>> 
>> >>> UserCreationForm doesn't call normalize_email and normalize_username 
>> >>> https://code.djangoproject.com/ticket/26719 
>> >>> Status: I sent some final edits to the PR and it should be ready for 
>> >>> commit tomorrow. 
>> >>> 
>> >>> Other possible blockers: 
>> >>> 
>> >>> Different manager for _base_manager and related descriptors 
>> >>> https://code.djangoproject.com/ticket/26749 
>> >>> django-hvad is broken by the manager inheritance refactor and it's 
>> >>> unclear if it can be adapted for the new behavior. 
>> >>> 
>> >>> Update decorator_from_middleware() to work with DEP5 style 
>> middleware. 
>> >>> https://code.djangoproject.com/ticket/26626 
>> >>> Design decision needed, see 
>> >>> 
>> https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion 
>> >>> 
>> >>> As long as no new issues pop up by tomorrow, I'm thinking to do the 
>> beta 
>> >>> release then. We might consider a "beta 2" release around 2 weeks 
>> later if 
>> >>> we decide to push fixes for the other two issues. 
>> >>> 
>> >>> On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote: 
>>  
>>  I'm postponing the release until next week as some release blockers 
>>  remain: 
>>  
>>  
>>  
>> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>>  
>>  
>>  On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote: 
>> > 
>> > Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit : 
>> >> 
>> >> There are a few small issues to finish up, but if all goes well, 
>> the 
>> >> beta release will happen sometime tomorrow (at least 24 hours from 
>> now). 
>> >> 
>> > 
>> > I'm a bit worried about https://code.djangoproject.com/ticket/26719 
>> > which could have security implications for 1.10. To be 
>> investigated... 
>> > 
>> > Claude 
>> > 
>>  
>> > 
>> >-- 
>> >You received this message because you are subscribed to the Google 
>> Groups "Django developers  (Contributions to Django itself)" group. 
>> >To unsubscribe from this group and stop receiving emails from it, send 
>> an email to django-develop...@googlegroups.com. 
>> >To post to this group, send email to django-d...@googlegroups.com. 
>> >Visit this group at https://groups.google.com/group/django-developers. 
>> >To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/94dd42e9-6940-4377-bd8e-7b285d0a63bc%40googlegroups.com.
>>  
>>
>> >For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/45820b89-1f2c-445a-95ba-b05744b18b5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-09-05 Thread Tim Graham 
As usual, the monthly bug fix release (1.10.1) is planned for tomorrow, 
September 1.

A remaining issue that could use some attention is about makemigrations and 
the new history consistency checks that were added in 1.10. These checks 
created problems in various multiple database setups, for example, with a 
read-only database. I've implemented a proposal to consult database 
routers, however, there remains a possibility for backwards-incompatibility 
as described in https://code.djangoproject.com/ticket/27142#comment:11. I'm 
okay with deferring the issue until next month if we can't come to a 
consensus. In particular, none of the ticket reporters have commented about 
whether or not the fix solves their issue.

PR: https://github.com/django/django/pull/7194 

On Saturday, July 30, 2016 at 9:20:46 PM UTC-4, Tim Graham wrote:
>
> The final release is on schedule for Monday, August 1.
>
> On Thursday, July 14, 2016 at 10:05:39 AM UTC-4, Markus Holtermann wrote:
>>
>> Thank you for the update, Tim. 
>>
>> #26888 will be taken care of by tomorrow. Either Marten or I are pushing 
>> a PR. 
>>
>> Cheers, 
>>
>> /Markus 
>>
>> On Thu, Jul 14, 2016 at 06:41:51AM -0700, Tim Graham wrote: 
>> >I'm planning for the release candidate on Monday. 
>> > 
>> >The one blocker is #26888  
>> - 
>> >RegexURLResolver doesn't work in threaded environments. 
>> > 
>> >On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote: 
>> >> 
>> >> The blocker is merged so I'll release the beta in a couple hours if no 
>> one 
>> >> stops me. 
>> >> 
>> >> On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote: 
>> >>> 
>> >>> The remaining blocker: 
>> >>> 
>> >>> UserCreationForm doesn't call normalize_email and normalize_username 
>> >>> https://code.djangoproject.com/ticket/26719 
>> >>> Status: I sent some final edits to the PR and it should be ready for 
>> >>> commit tomorrow. 
>> >>> 
>> >>> Other possible blockers: 
>> >>> 
>> >>> Different manager for _base_manager and related descriptors 
>> >>> https://code.djangoproject.com/ticket/26749 
>> >>> django-hvad is broken by the manager inheritance refactor and it's 
>> >>> unclear if it can be adapted for the new behavior. 
>> >>> 
>> >>> Update decorator_from_middleware() to work with DEP5 style 
>> middleware. 
>> >>> https://code.djangoproject.com/ticket/26626 
>> >>> Design decision needed, see 
>> >>> 
>> https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion 
>> >>> 
>> >>> As long as no new issues pop up by tomorrow, I'm thinking to do the 
>> beta 
>> >>> release then. We might consider a "beta 2" release around 2 weeks 
>> later if 
>> >>> we decide to push fixes for the other two issues. 
>> >>> 
>> >>> On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote: 
>>  
>>  I'm postponing the release until next week as some release blockers 
>>  remain: 
>>  
>>  
>>  
>> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>>  
>>  
>>  On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote: 
>> > 
>> > Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit : 
>> >> 
>> >> There are a few small issues to finish up, but if all goes well, 
>> the 
>> >> beta release will happen sometime tomorrow (at least 24 hours from 
>> now). 
>> >> 
>> > 
>> > I'm a bit worried about https://code.djangoproject.com/ticket/26719 
>> > which could have security implications for 1.10. To be 
>> investigated... 
>> > 
>> > Claude 
>> > 
>>  
>> > 
>> >-- 
>> >You received this message because you are subscribed to the Google 
>> Groups "Django developers  (Contributions to Django itself)" group. 
>> >To unsubscribe from this group and stop receiving emails from it, send 
>> an email to django-develop...@googlegroups.com. 
>> >To post to this group, send email to django-d...@googlegroups.com. 
>> >Visit this group at https://groups.google.com/group/django-developers. 
>> >To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/94dd42e9-6940-4377-bd8e-7b285d0a63bc%40googlegroups.com.
>>  
>>
>> >For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/504c5be0-9cc5-4af7-8b0d-1d254ab388aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-07-30 Thread Tim Graham 
The final release is on schedule for Monday, August 1.

On Thursday, July 14, 2016 at 10:05:39 AM UTC-4, Markus Holtermann wrote:
>
> Thank you for the update, Tim. 
>
> #26888 will be taken care of by tomorrow. Either Marten or I are pushing 
> a PR. 
>
> Cheers, 
>
> /Markus 
>
> On Thu, Jul 14, 2016 at 06:41:51AM -0700, Tim Graham wrote: 
> >I'm planning for the release candidate on Monday. 
> > 
> >The one blocker is #26888  
> - 
> >RegexURLResolver doesn't work in threaded environments. 
> > 
> >On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote: 
> >> 
> >> The blocker is merged so I'll release the beta in a couple hours if no 
> one 
> >> stops me. 
> >> 
> >> On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote: 
> >>> 
> >>> The remaining blocker: 
> >>> 
> >>> UserCreationForm doesn't call normalize_email and normalize_username 
> >>> https://code.djangoproject.com/ticket/26719 
> >>> Status: I sent some final edits to the PR and it should be ready for 
> >>> commit tomorrow. 
> >>> 
> >>> Other possible blockers: 
> >>> 
> >>> Different manager for _base_manager and related descriptors 
> >>> https://code.djangoproject.com/ticket/26749 
> >>> django-hvad is broken by the manager inheritance refactor and it's 
> >>> unclear if it can be adapted for the new behavior. 
> >>> 
> >>> Update decorator_from_middleware() to work with DEP5 style middleware. 
> >>> https://code.djangoproject.com/ticket/26626 
> >>> Design decision needed, see 
> >>> 
> https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion 
> >>> 
> >>> As long as no new issues pop up by tomorrow, I'm thinking to do the 
> beta 
> >>> release then. We might consider a "beta 2" release around 2 weeks 
> later if 
> >>> we decide to push fixes for the other two issues. 
> >>> 
> >>> On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote: 
>  
>  I'm postponing the release until next week as some release blockers 
>  remain: 
>  
>  
>  
> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>  
>  
>  On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote: 
> > 
> > Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit : 
> >> 
> >> There are a few small issues to finish up, but if all goes well, 
> the 
> >> beta release will happen sometime tomorrow (at least 24 hours from 
> now). 
> >> 
> > 
> > I'm a bit worried about https://code.djangoproject.com/ticket/26719 
> > which could have security implications for 1.10. To be 
> investigated... 
> > 
> > Claude 
> > 
>  
> > 
> >-- 
> >You received this message because you are subscribed to the Google Groups 
> "Django developers  (Contributions to Django itself)" group. 
> >To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-develop...@googlegroups.com . 
> >To post to this group, send email to django-d...@googlegroups.com 
> . 
> >Visit this group at https://groups.google.com/group/django-developers. 
> >To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/94dd42e9-6940-4377-bd8e-7b285d0a63bc%40googlegroups.com.
>  
>
> >For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/34304173-2186-4dcb-9e0e-98a1d86c960a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-07-14 Thread Markus Holtermann 

Thank you for the update, Tim.

#26888 will be taken care of by tomorrow. Either Marten or I are pushing
a PR.

Cheers,

/Markus

On Thu, Jul 14, 2016 at 06:41:51AM -0700, Tim Graham wrote:

I'm planning for the release candidate on Monday.

The one blocker is #26888  -
RegexURLResolver doesn't work in threaded environments.

On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote:


The blocker is merged so I'll release the beta in a couple hours if no one
stops me.

On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote:


The remaining blocker:

UserCreationForm doesn't call normalize_email and normalize_username
https://code.djangoproject.com/ticket/26719
Status: I sent some final edits to the PR and it should be ready for
commit tomorrow.

Other possible blockers:

Different manager for _base_manager and related descriptors
https://code.djangoproject.com/ticket/26749
django-hvad is broken by the manager inheritance refactor and it's
unclear if it can be adapted for the new behavior.

Update decorator_from_middleware() to work with DEP5 style middleware.
https://code.djangoproject.com/ticket/26626
Design decision needed, see
https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion

As long as no new issues pop up by tomorrow, I'm thinking to do the beta
release then. We might consider a "beta 2" release around 2 weeks later if
we decide to push fixes for the other two issues.

On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote:


I'm postponing the release until next week as some release blockers
remain:


https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker

On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote:


Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :


There are a few small issues to finish up, but if all goes well, the
beta release will happen sometime tomorrow (at least 24 hours from now).



I'm a bit worried about https://code.djangoproject.com/ticket/26719
which could have security implications for 1.10. To be investigated...

Claude





--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/94dd42e9-6940-4377-bd8e-7b285d0a63bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/20160714140527.GC5382%40inel.local.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: status of 1.10 release blockers

2016-07-14 Thread Tim Graham 
I'm planning for the release candidate on Monday.

The one blocker is #26888  - 
RegexURLResolver doesn't work in threaded environments.

On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote:
>
> The blocker is merged so I'll release the beta in a couple hours if no one 
> stops me.
>
> On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote:
>>
>> The remaining blocker:
>>
>> UserCreationForm doesn't call normalize_email and normalize_username
>> https://code.djangoproject.com/ticket/26719
>> Status: I sent some final edits to the PR and it should be ready for 
>> commit tomorrow.
>>
>> Other possible blockers:
>>
>> Different manager for _base_manager and related descriptors
>> https://code.djangoproject.com/ticket/26749
>> django-hvad is broken by the manager inheritance refactor and it's 
>> unclear if it can be adapted for the new behavior.
>>
>> Update decorator_from_middleware() to work with DEP5 style middleware.
>> https://code.djangoproject.com/ticket/26626
>> Design decision needed, see 
>> https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion
>>
>> As long as no new issues pop up by tomorrow, I'm thinking to do the beta 
>> release then. We might consider a "beta 2" release around 2 weeks later if 
>> we decide to push fixes for the other two issues.
>>
>> On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote:
>>>
>>> I'm postponing the release until next week as some release blockers 
>>> remain:
>>>
>>>
>>> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>>>
>>> On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote:

 Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :
>
> There are a few small issues to finish up, but if all goes well, the 
> beta release will happen sometime tomorrow (at least 24 hours from now).
>

 I'm a bit worried about https://code.djangoproject.com/ticket/26719 
 which could have security implications for 1.10. To be investigated...

 Claude

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/94dd42e9-6940-4377-bd8e-7b285d0a63bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-06-21 Thread Tim Graham 
The blocker is merged so I'll release the beta in a couple hours if no one 
stops me.

On Monday, June 20, 2016 at 9:10:12 PM UTC-4, Tim Graham wrote:
>
> The remaining blocker:
>
> UserCreationForm doesn't call normalize_email and normalize_username
> https://code.djangoproject.com/ticket/26719
> Status: I sent some final edits to the PR and it should be ready for 
> commit tomorrow.
>
> Other possible blockers:
>
> Different manager for _base_manager and related descriptors
> https://code.djangoproject.com/ticket/26749
> django-hvad is broken by the manager inheritance refactor and it's unclear 
> if it can be adapted for the new behavior.
>
> Update decorator_from_middleware() to work with DEP5 style middleware.
> https://code.djangoproject.com/ticket/26626
> Design decision needed, see 
> https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion
>
> As long as no new issues pop up by tomorrow, I'm thinking to do the beta 
> release then. We might consider a "beta 2" release around 2 weeks later if 
> we decide to push fixes for the other two issues.
>
> On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote:
>>
>> I'm postponing the release until next week as some release blockers 
>> remain:
>>
>>
>> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>>
>> On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote:
>>>
>>> Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :

 There are a few small issues to finish up, but if all goes well, the 
 beta release will happen sometime tomorrow (at least 24 hours from now).

>>>
>>> I'm a bit worried about https://code.djangoproject.com/ticket/26719 
>>> which could have security implications for 1.10. To be investigated...
>>>
>>> Claude
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ce12f95b-4e36-47f3-9810-7f57e8e76941%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-06-20 Thread Tim Graham 
The remaining blocker:

UserCreationForm doesn't call normalize_email and normalize_username
https://code.djangoproject.com/ticket/26719
Status: I sent some final edits to the PR and it should be ready for commit 
tomorrow.

Other possible blockers:

Different manager for _base_manager and related descriptors
https://code.djangoproject.com/ticket/26749
django-hvad is broken by the manager inheritance refactor and it's unclear 
if it can be adapted for the new behavior.

Update decorator_from_middleware() to work with DEP5 style middleware.
https://code.djangoproject.com/ticket/26626
Design decision needed, see 
https://groups.google.com/d/topic/django-developers/hNQIaYcN3xM/discussion

As long as no new issues pop up by tomorrow, I'm thinking to do the beta 
release then. We might consider a "beta 2" release around 2 weeks later if 
we decide to push fixes for the other two issues.

On Saturday, June 18, 2016 at 8:05:32 PM UTC-4, Tim Graham wrote:
>
> I'm postponing the release until next week as some release blockers remain:
>
>
> https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker
>
> On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote:
>>
>> Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :
>>>
>>> There are a few small issues to finish up, but if all goes well, the 
>>> beta release will happen sometime tomorrow (at least 24 hours from now).
>>>
>>
>> I'm a bit worried about https://code.djangoproject.com/ticket/26719 
>> which could have security implications for 1.10. To be investigated...
>>
>> Claude
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4b474f69-e71a-4467-971f-2c15ef32dc54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-06-18 Thread Tim Graham 
I'm postponing the release until next week as some release blockers remain:

https://code.djangoproject.com/query?status=!closed&severity=Release%20blocker

On Friday, June 17, 2016 at 5:33:04 PM UTC-4, Claude Paroz wrote:
>
> Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :
>>
>> There are a few small issues to finish up, but if all goes well, the beta 
>> release will happen sometime tomorrow (at least 24 hours from now).
>>
>
> I'm a bit worried about https://code.djangoproject.com/ticket/26719 which 
> could have security implications for 1.10. To be investigated...
>
> Claude
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c9f192b3-e9d0-4310-bf26-e3cbbf334462%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-06-17 Thread Claude Paroz 
Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit :
>
> There are a few small issues to finish up, but if all goes well, the beta 
> release will happen sometime tomorrow (at least 24 hours from now).
>

I'm a bit worried about https://code.djangoproject.com/ticket/26719 which 
could have security implications for 1.10. To be investigated...

Claude

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1ba746a8-f420-4230-be18-4ec45504adfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-06-17 Thread Tim Graham 
There are a few small issues to finish up, but if all goes well, the beta 
release will happen sometime tomorrow (at least 24 hours from now).

On Thursday, May 19, 2016 at 2:08:59 PM UTC-4, Tim Graham wrote:
>
> The CSRF patch is merged. I'm a bit stuck on the middleware one, however, 
> I don't think it's a blocker for alpha. I think I'll create the stable 
> branch and make the release later today (in about 7 hours), unless there 
> are objections.
>
> On Wednesday, May 18, 2016 at 10:03:17 PM UTC-4, Tim Graham wrote:
>>
>> A couple issues remain before the alpha release:
>>
>> Issue: Fixing some new-style SessionMiddleware to process the response 
>> even if the view raises an exception.
>> Status: This is somewhat in design decision needed if anyone would like 
>> to take a look and offer feedback. I'll look at it more closely tomorrow.
>> https://github.com/django/django/pull/6618
>>
>> Issue: Made CSRF tokens change every request.
>> Status: Awaiting final (trivial, I believe) updates from Shai.
>> https://github.com/django/django/pull/5605
>>
>> Issue: i18n test failures on Windows
>> Status: Awaiting someone with interest in Windows i18n to investigate. 
>> I'm not considering this a blocker for the release (alpha or otherwise) 
>> since we can't guarantee sometime with Windows expertise to fix the issue.
>> https://code.djangoproject.com/ticket/25677
>>
>> I hope to resolve these issues and make the alpha release tomorrow or 
>> Friday.
>>
>> On Saturday, May 14, 2016 at 7:40:32 PM UTC-4, Tim Graham wrote:
>>>
>>> Time to kickoff the progress tracker for the next major release!
>>>
>>> At this time, I'm considering master feature frozen besides the tickets 
>>> marked "ready for checkin" [1] and those tagged "1.10" [2]. Let me know if 
>>> I missed anything critical.
>>>
>>> I'll continue working with the ticket owners to polish those patches. 
>>> I'll also continue merging bug fixes until we create the stable/1.10 branch 
>>> and issue the alpha release, which I'd like to do sometime next week.
>>>
>>> [1] 
>>> https://code.djangoproject.com/query?status=assigned&status=new&stage=Ready+for+checkin&col=id&col=summary&col=status&col=owner&col=type&col=version&order=priority
>>> [2] 
>>> https://code.djangoproject.com/query?status=assigned&status=new&keywords=~1.10&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=version&col=changetime&desc=1&order=changetime
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/fe6a92c8-d4ca-41b5-8169-990d0f79dc14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-05-19 Thread Tim Graham 
The CSRF patch is merged. I'm a bit stuck on the middleware one, however, I 
don't think it's a blocker for alpha. I think I'll create the stable branch 
and make the release later today (in about 7 hours), unless there are 
objections.

On Wednesday, May 18, 2016 at 10:03:17 PM UTC-4, Tim Graham wrote:
>
> A couple issues remain before the alpha release:
>
> Issue: Fixing some new-style SessionMiddleware to process the response 
> even if the view raises an exception.
> Status: This is somewhat in design decision needed if anyone would like to 
> take a look and offer feedback. I'll look at it more closely tomorrow.
> https://github.com/django/django/pull/6618
>
> Issue: Made CSRF tokens change every request.
> Status: Awaiting final (trivial, I believe) updates from Shai.
> https://github.com/django/django/pull/5605
>
> Issue: i18n test failures on Windows
> Status: Awaiting someone with interest in Windows i18n to investigate. I'm 
> not considering this a blocker for the release (alpha or otherwise) since 
> we can't guarantee sometime with Windows expertise to fix the issue.
> https://code.djangoproject.com/ticket/25677
>
> I hope to resolve these issues and make the alpha release tomorrow or 
> Friday.
>
> On Saturday, May 14, 2016 at 7:40:32 PM UTC-4, Tim Graham wrote:
>>
>> Time to kickoff the progress tracker for the next major release!
>>
>> At this time, I'm considering master feature frozen besides the tickets 
>> marked "ready for checkin" [1] and those tagged "1.10" [2]. Let me know if 
>> I missed anything critical.
>>
>> I'll continue working with the ticket owners to polish those patches. 
>> I'll also continue merging bug fixes until we create the stable/1.10 branch 
>> and issue the alpha release, which I'd like to do sometime next week.
>>
>> [1] 
>> https://code.djangoproject.com/query?status=assigned&status=new&stage=Ready+for+checkin&col=id&col=summary&col=status&col=owner&col=type&col=version&order=priority
>> [2] 
>> https://code.djangoproject.com/query?status=assigned&status=new&keywords=~1.10&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=version&col=changetime&desc=1&order=changetime
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e0f92fd0-1aa4-4141-b68c-b77a707606fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: status of 1.10 release blockers

2016-05-18 Thread Tim Graham 
A couple issues remain before the alpha release:

Issue: Fixing some new-style SessionMiddleware to process the response even 
if the view raises an exception.
Status: This is somewhat in design decision needed if anyone would like to 
take a look and offer feedback. I'll look at it more closely tomorrow.
https://github.com/django/django/pull/6618

Issue: Made CSRF tokens change every request.
Status: Awaiting final (trivial, I believe) updates from Shai.
https://github.com/django/django/pull/5605

Issue: i18n test failures on Windows
Status: Awaiting someone with interest in Windows i18n to investigate. I'm 
not considering this a blocker for the release (alpha or otherwise) since 
we can't guarantee sometime with Windows expertise to fix the issue.
https://code.djangoproject.com/ticket/25677

I hope to resolve these issues and make the alpha release tomorrow or 
Friday.

On Saturday, May 14, 2016 at 7:40:32 PM UTC-4, Tim Graham wrote:
>
> Time to kickoff the progress tracker for the next major release!
>
> At this time, I'm considering master feature frozen besides the tickets 
> marked "ready for checkin" [1] and those tagged "1.10" [2]. Let me know if 
> I missed anything critical.
>
> I'll continue working with the ticket owners to polish those patches. I'll 
> also continue merging bug fixes until we create the stable/1.10 branch and 
> issue the alpha release, which I'd like to do sometime next week.
>
> [1] 
> https://code.djangoproject.com/query?status=assigned&status=new&stage=Ready+for+checkin&col=id&col=summary&col=status&col=owner&col=type&col=version&order=priority
> [2] 
> https://code.djangoproject.com/query?status=assigned&status=new&keywords=~1.10&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=version&col=changetime&desc=1&order=changetime
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/311634c5-e4cf-48ba-b2c3-91ac40c3ce8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

status of 1.10 release blockers

2016-05-14 Thread Tim Graham 
Time to kickoff the progress tracker for the next major release!

At this time, I'm considering master feature frozen besides the tickets 
marked "ready for checkin" [1] and those tagged "1.10" [2]. Let me know if 
I missed anything critical.

I'll continue working with the ticket owners to polish those patches. I'll 
also continue merging bug fixes until we create the stable/1.10 branch and 
issue the alpha release, which I'd like to do sometime next week.

[1] 
https://code.djangoproject.com/query?status=assigned&status=new&stage=Ready+for+checkin&col=id&col=summary&col=status&col=owner&col=type&col=version&order=priority
[2] 
https://code.djangoproject.com/query?status=assigned&status=new&keywords=~1.10&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=version&col=changetime&desc=1&order=changetime

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/36f569dd-2fe3-4caf-ae3d-e04b71e3d87d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.