Re: status of 1.10 release blockers

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-de

Re: status of 1.10 release blockers

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 exa

Re: status of 1.10 release blockers

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,

Re: status of 1.10 release blockers

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

Re: status of 1.10 release blockers

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

Re: status of 1.10 release blockers

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 >

Re: status of 1.10 release blockers

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

Re: status of 1.10 release blockers

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 : >> >> Ther

Re: status of 1.10 release blockers

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

Re: status of 1.10 release blockers

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 t

Re: status of 1.10 release blockers

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 w

Re: status of 1.10 release blockers

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 to

status of 1.10 release blockers

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