On Sat, Aug 6, 2011 at 6:16 PM, Srik <srikanth...@gmail.com> wrote: > Hello All, > > I believe https://code.djangoproject.com/wiki/Version1.4Roadmap needs > update badly considering 1.3 was released 4 months ago and 1.4 Roadmap > was never updated.
Agreed -- we haven't been very good with public plans for the 1.4 cycle. Internally, the core team had some discussions about some more aggressive dates that would lead to faster cycles, but those dates sailed past a long time ago. At this point, I think we should be aiming at DjangoCon as a deadline for the Alpha; with beta and final following at roughly 1 month increments after that, which would produce a 1.4 release around the end of November. However, I hasten to add: 1) I haven't discussed these dates with the rest of the core team, 2) The real impediment to getting a release out the door is having someone who has the spare time to manage the release process. That's been me for the last two releases; I'm fairly certain I won't have the spare cycles to make it three in a row. > There seems to be good amount of work going on as per commits to trunk > but what exactly are the goals of 1.4. > > Will it be mainly bug fix (closing existing tickets) or can we expect > any new features (If so do we have a list elsewhere towards which > developers are working)? The feature list of 1.4 isn't likely to have a bunch of massive features like 1.2; it's more likely to be like 1.3. That is, a couple of big features, and a bunch of bugfixes. *Which* features is mostly up to the community. Essentially, the final feature list for 1.4 will be determined by the list of RFC patches that are submitted. Some of those will be contributed by core developers, some will come from the general community. Bigger features will need some buy-in from a core developer if they're going to get committed. The lesson we've learned from the 1.1 and 1.2 cycles is that it doesn't matter what someone wants to put on a feature list -- what matters is actually producing the patch. So, it's better to set a date and cut a release based on the features available at that date, rather than wait for delivery of a feature that many people have expressed an interest in, but nobody has worked on. The moral of this story -- if there's a feature you want, *you* have to make it happen, by writing patches, engaging the community, and convincing a core developer that it's a must-have feature with community support. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
