After reading through this entire thread it seems that there are a few points to be consolidated:
1. DVCS concerns should be pushed to 1.4+ and in the meantime, mirrors are fine. 2. The management of the current Trac system has organizational issues - i.e. many people don't know who committers are and whether they should aggressively manage tickets since they have alot of power. Nonetheless, these are manageable for now. 3. Version 1.3 should be feature-light I would propose the following: 1. Finish version 1.2 2. Assign all of these tickets to 1.3 and nothing else: http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&milestone=&has_patch=1&order=priority These all have a patch and no milestone. 3. Go through all of the newly assigned 'milestone 1.3' tickets and either close them as wontfix, apply the patch, or move them to a new milestone called 'Next Major Release'. 4. Release version 1.3 5. Evaluate other stuff like major DVCS changes, Trac changes, etc... I think this would be the best timeline for the community and is the best way to maintain a good relationship with the people who have had patches waiting for over a year. Marking them as wontfix is fine, as long as some movement is made. Cheers, Adam On Apr 22, 2:37 am, Thomas Guettler <h...@tbz-pariv.de> wrote: > The plan to make 1.3 a feature light release with focus on > fixing old bugs and tickets, was a good one. > > I have some tickets in trac which are quite old, too. But it has been > a very long time, since I reviewed tickets of other people, too. > > Sometimes I think the development process is slow. But that's wrong. > The development is just in parts I don't need up to now (for example multi db > support). > > Thomas > > > > > > Jacob Kaplan-Moss wrote: > > Hi folks -- > > > I'd like to try to reboot the discussion that's been going on about > > Django's development process. > > > I'm finding the current thread incredibly demoralizing: there's a > > bunch of frustration being expressed, and I hear that, but I'm having > > trouble finding any concrete suggestions. Instead, the thread has > > devolved into just going around in circles on the same small handful > > of issues. > > > So: here's your chance. You have suggestions about Django's > > development process? Make them. I'm listening. > > > Jacob > > -- > Thomas Guettler,http://www.thomas-guettler.de/ > E-Mail: guettli (*) thomas-guettler + de > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
