On Tue, 2009-03-17 at 17:19 -0400, Eric S. Raymond wrote: > Mark de Wever <[email protected]>: > > > I think the only way we're going to get > > > more user testing is by shipping "stable" releases more often, which > > > is to say seriously shortening our development cycle. > > > > Well the goal was to start to think about how to achieve that wish. > > Since I've no real ideas about what we could do to improve the situation > > I just wanted to start the discussion. > > And quite rightly. This is a good time to have it. > > > I'm not sure whether the shortening the development cycle really helps > > (I think not) but we could try it. The last time we also discussed the > > idea of a half year cycle and rejected it. But since the current model > > also doesn't 'work' in this regard we can at least try it. So if we aim > > for half a year that would be the middle of September, which would also > > fit with gsoc (if we get in). > > I have also, independently, been thinking that September 2009 would > make a good target date for 1.8. That timing seems about right for > both of the major 1.7 projects I know are already scheduled to have > landed and gotten some testing.
Personally I would love it if we could get our release cycle down to 6 months instead of 12 (more like 14) months. I think that one of the problems with our current release cycle is that people begin with thinking that 12 months is forever to develop something, so they do nothing at all. It is somewhat demoralizing to think of developing something and not see it in a stable version for 12 months! Then time runs short, and people scramble: "If I don't get my feature in NOW then it won't make it for 12 whole months!!" If we could reduce the release cycle to 6 months, these effects would be lessened. I don't see why we can't be agile enough to have a 6 month release cycle, and would love it if we could achieve this. David _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
