Time based releases?
Nikolaj Hald Nielsen
nhnfreespirit at gmail.com
Fri Mar 27 10:31:14 CET 2009
> I think the idea of a concrete release cycle is good---it gives us focus and
> allows us to work hard on new features then switch to bugfix mode. But I don't
> see why we need to fix the release cycle for *all* our releases beforehand---
> why not just decide the length of the next release cycle after each release?
> Most likely we'll have more information at hand, and can tailor it to our
> specific needs.
+1
But it might make sense to set a date for next release, feature freeze
and so on as soon as the previous release is out. That will give
everyone a better idea of how much tie there really is to add big new
features. Meaning that as soon as 2.1.0 is out, we set dates for 2.1.1
( and possibly even for 2.2.0 ). That makes sense to me, but going
beyond that does not.
- Nikolaj
More information about the Amarok-devel
mailing list