Instead of aiming for one huge patch to be merged at the end of the summer, I'd suggest to think about whether you can break up the work in chunks that can be merged incrementally. This should decrease the risk that comes with a huge patch going stale and makes code review much easier.
It's helpful if you can add your other commitments for the summer such as holidays, vacations, etc. On Monday, March 14, 2016 at 6:15:34 AM UTC-4, akki wrote: > > >> you can't have identical indexes defined in multiple ways with the same >> names. >> > > Yes, I will be checking for the duplications at the autodetector level > itself. We need to take care that no two indexes are for the same fields, > and none of them have a clashing name. On such an occurrence, we can raise > an error like "Multiple indexes have been set for 'field1' " or merge them > ourself internally (if they mean exactly the same). > > -- 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/70167af7-890c-412a-a380-91b638e50884%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
