On 24 Feb 2008, at 18:16, Gunnar Wolf wrote: > Taher Shihadeh dijo [Sun, Feb 24, 2008 at 03:36:30PM +0100]: >> How about a fixed release cycle? >> >> I realize it's very complicated to have one when there's not a big >> company behind the effort, especially since there are a lot of >> factors involved besides the commitment and availability of each >> developer. >> >> But it really makes for a great PR headline, even if it's only an >> approximate schedule. Not to say that it is the only factor, but >> everyone can see the effect on popularity that the 6 month policy >> between releases had on Ubuntu versus Debian's "it will be ready >> when it's ready", for example. > > Well, you can also compare quality, and you'll get quite a different > picture ;-) > > Now, on a more objective note: a development effort is quite different > to an integration effort. I am of the opinion that development efforts > are basically incompatible with a fixed-time release policy. You have > many processes that are bound to reaching many minor milestones at > once... Launching a new version just because "it's the right time" > means very little to me.
Fixed time releases have been working fairly well for GNOME, for instance. Actually, I would be more for some kind of fixed release schedule rather than for repeating the almost-three-years-long release of Cherokee 0.6.0. I do know that I screwed big time with the planing, so whatever release schedule go for, it should not be "release when it is ready". It has proved not to work for our environment. IMO, the core team ought to strictly follow the roadmap that we discussed yesterday. As soon as the new features on the list are implemented it would be time for a pre-release. Then, we would wait a few days to check whether it is stable and ensure that there are no regressions.. after which the new release would be ready. Of course, the shorter this process takes, the better. -- Greetings, alo. http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
