Hey Tim, Thanks for the update. Could you check if #24282 is fixed by my PR as well and assign it to me in case it is. The error message looks familiar to the one I commented on the PR. Thanks.
/Markus On February 13, 2015 2:33:38 AM GMT+01:00, Tim Graham <timogra...@gmail.com> wrote: >Status of release blockers: > >#24320 <https://code.djangoproject.com/ticket/24320> Unable to >serialize >UUIDField when running dumpdata with JSON format ><https://code.djangoproject.com/ticket/24320> >Status: I wrote a failing test and will try to write a patch tomorrow >if no >one else takes a look first. > >#24289 <https://code.djangoproject.com/ticket/24289> Is usage of >many_to_one and one_to_many terms confusing for relation flags? ><https://code.djangoproject.com/ticket/24289> >Status: We are waiting for feedback/confirmation from Anssi and Russ >about >the direction to take here. > >#24225 <https://code.djangoproject.com/ticket/24225> KeyError when >migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3) ><https://code.djangoproject.com/ticket/24225> >#24264 <https://code.djangoproject.com/ticket/24264> foreign key >constraint >error migrating integer pk to CharField ><https://code.djangoproject.com/ticket/24264> >Status: Markus has a patch which addresses both issues. It's in good >shape >and should be ready for commit soon. > >#24282 <https://code.djangoproject.com/ticket/24282> Cannot Modify >Foreign >Keys Within Data Migrations ><https://code.djangoproject.com/ticket/24282> >Status: This is awaiting a test case to reproduce the issue (I'll >investigate tomorrow if no one else does). > >Here is the filter for 1.8 release blockers as well as issues tagged >1.8 >beta or 1.8 and thus are on my radar to make a decision on in the next >couple days: >https://code.djangoproject.com/query?status=assigned&status=new&version=1.8alpha1&severity=Release+blocker&or&keywords=~1.8-beta&status=assigned&status=new&or&keywords=~1.8&status=assigned&status=new&col=id&col=summary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime > >On Wednesday, February 4, 2015 at 9:45:33 AM UTC-5, Tim Graham wrote: >> >> Reminder that the 1.8 beta release is scheduled for twelve days from >now: >> Monday, February 16. >> >> Please check this filter for remaining blockers for beta: >> >> >> >https://code.djangoproject.com/query?status=assigned&status=new&version=1.8alpha1&severity=Release+blocker&or&status=assigned&status=new&keywords=~1.8-beta&col=id&col=summary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime >> >> I'll follow up next week to ensure we have owners for any issues that > >> remain after the weekend. >> >> On Thursday, January 15, 2015 at 8:30:04 PM UTC-5, Tim Graham wrote: >>> >>> I think master is stabilizing and the number of unsolved regressions > >>> should be ~0 by tomorrow. I'd like to release the alpha around 2100 >UTC >>> tomorrow +/- ~4 hours depending on how things go with the remaining >issues. >>> Let me know if there is anything you think needs to be in the alpha >that >>> wouldn't meet this deadline. >>> >>> On Tuesday, January 13, 2015 at 1:50:26 AM UTC-5, Tino de Bruijn >wrote: >>>> >>>> Congratulations! Looks like you've steadily moved it through. >>>> >>>> Tino >>>> >>>> On Tue, Jan 13, 2015 at 3:25 AM, Tim Graham <timog...@gmail.com> >wrote: >>>> >>>>> We did it -- all features are in or out for alpha. Please consider > >>>>> master frozen for new features until we cut the stable/1.8.x >branch later >>>>> this week. Feel free to commit code cleanups and/or bug fixes >until then. >>>>> >>>>> >>>>> On Friday, January 9, 2015 at 1:14:02 PM UTC-5, Tim Graham wrote: >>>>>> >>>>>> Here is the fifth update with several days to go until alpha. I >>>>>> believe we are on track for a feature freeze at the end of day on >Monday. >>>>>> Let's see how things go, but I'd like to cut the stable/1.8.x >branch and >>>>>> issue the alpha release by the following Friday (a week from >today). >>>>>> >>>>>> New blockers: >>>>>> >>>>>> #24075 <https://code.djangoproject.com/ticket/24075> - Can't >migrate >>>>>> contenttypes and auth to zero >>>>>> <https://code.djangoproject.com/ticket/24075> >>>>>> Owner: Simon >>>>>> Status: This is an existing issue on 1.7, but addressing it seems >to >>>>>> require (or at least, would be a lot easier) with the proposed >new feature >>>>>> of adding a "plan" argument to the post_migrate() signal. There >is a patch >>>>>> in the works. >>>>>> >>>>>> Resolved since last time: >>>>>> >>>>>> #23861 - >>>>>> <https://code.djangoproject.com/ticket/23861> Fields referenced >in >>>>>> migrations cannot be (re)moved, even if migrations have been >squashed >>>>>> <https://code.djangoproject.com/ticket/23861> >>>>>> Owner: Tim >>>>>> Now: I polished and committed the patch for this. >>>>>> Last time: I committed a patch for the second ticket and will >polish >>>>>> the patch for the first issue. >>>>>> >>>>>> Most of the issues tagged "1.8-alpha" have been completed or >deferred. >>>>>> The two main ones that remain are "Case/When expressions" and >"Allowing >>>>>> expressions to be used in order_by queryset method." Depending on >what >>>>>> progress is made over the weekend on these issues, they may or >may not make >>>>>> it into 1.8. >>>>>> https://code.djangoproject.com/query?status=assigned&; >>>>>> status=new&keywords=~1.8-alpha >>>>>> >>>>>> On Saturday, January 3, 2015 at 1:19:25 PM UTC-5, jdunck wrote: >>>>>>> >>>>>>> Thank you, Tim, for shepherding this. >>>>>>> On Jan 3, 2015 8:09 AM, "Tim Graham" <timog...@gmail.com> 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 later >>>>>>>> just to give some time for some extra polish in case any large >patches are >>>>>>>> committed next weekend. >>>>>>>> >>>>>>>> #23861 - >>>>>>>> <https://code.djangoproject.com/ticket/23861> Fields referenced >in >>>>>>>> migrations cannot be (re)moved, even if migrations have been >squashed >>>>>>>> <https://code.djangoproject.com/ticket/23861> >>>>>>>> #23891 <https://code.djangoproject.com/ticket/23891> - Revise >>>>>>>> deprecation / removal timeline for IPAddressField >>>>>>>> <https://code.djangoproject.com/ticket/23891> (resolved) >>>>>>>> Owner: Tim >>>>>>>> Now: I committed a patch for the second ticket and will polish >the >>>>>>>> patch for the first issue. >>>>>>>> Last time: I've implemented the system check solution I >proposed and >>>>>>>> am waiting for review and/or concerns with this approach. >>>>>>>> >>>>>>>> After completing the issue above, I'll prioritize any issues >here: >>>>>>>> https://code.djangoproject.com/query?status=assigned&; >>>>>>>> status=new&keywords=~1.8-alpha >>>>>>>> >>>>>>>> Resolved since last time: >>>>>>>> >>>>>>>> #22340 - >>>>>>>> <https://code.djangoproject.com/ticket/22340> Legacy Table >Creation >>>>>>>> Methods Not Properly Deprecated >>>>>>>> <https://code.djangoproject.com/ticket/22340> >>>>>>>> Owner: Tim >>>>>>>> Now: Resolved this by removing the deprecation as discussed in >the >>>>>>>> ticket. >>>>>>>> Last time: I took a closer look at this and don't think we need >to >>>>>>>> do this deprecation at all as it doesn't seem to offer any >benefits. See >>>>>>>> the ticket for details. >>>>>>>> >>>>>>>> #23745 - Migrations migrate is slow >>>>>>>> <https://code.djangoproject.com/ticket/23745> >>>>>>>> Owner: Claude/Markus >>>>>>>> Now: Patch committed; thanks to Markus and Claude. >>>>>>>> Last time: I committed the test that Markus wrote and Claude >>>>>>>> incorporated a fix from Markus so the branch appears about >ready for merge. >>>>>>>> Markus will give it another review. >>>>>>>> >>>>>>>> -- >>>>>>>> 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 >http://groups.google.com/group/django-developers >>>>>>>> . >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/django-developers/ >>>>>>>> b196f095-530c-45ec-9b21-82fcd1c06ed8%40googlegroups.com >>>>>>>> ><https://groups.google.com/d/msgid/django-developers/b196f095-530c-45ec-9b21-82fcd1c06ed8%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> 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-develop...@googlegroups.com. >>>>> To post to this group, send email to django-d...@googlegroups.com. >>>>> Visit this group at >http://groups.google.com/group/django-developers. >>>>> To view this discussion on the web visit >>>>> >https://groups.google.com/d/msgid/django-developers/15aaad79-b702-4bb4-a3dd-b341ed140aab%40googlegroups.com > >>>>> ><https://groups.google.com/d/msgid/django-developers/15aaad79-b702-4bb4-a3dd-b341ed140aab%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ADA24400-A74D-4470-B271-82AC55E70009%40markusholtermann.eu. For more options, visit https://groups.google.com/d/optout.
