...

• 1.2 (Feb 2005)
• 1.3 (August 2005) 6 months
• 1.4 (July 2006) 11 months
• 1.5 (March 2008) 18 months
• 1.6*(March 2010) 24 months *=projected

Despite a vastly larger developer community, more committers, better organizational support (DuraSpace),
and better software management tools and processes, our release cycles continue to lengthen. This not only creates the impression of a languishing project, but needlessly delays important new features and bug fixes to our adopter community.

...

Comments

What do you think?

Mwood 19:38, 10 March 2010 (UTC) A roughly periodic release schedule does force some planning to select a manageable amount of development within the interval. I think that's the real problem: we don't get the community together often enough to talk over what to do next, and then follow through. We get lots of ideas but we could do better prioritizing and scheduling them. We might benefit as well from earlier branching so that things which aren't ready for release.next always have somewhere to go.

...

(NOTE: If you feel any of the above statements misrepresent our discussion, please let me know! – TimDonohue)

Questions left unanswered:

...