On 11/05/2010, at 22:24, James Pearson wrote: > Do we get any "safety" guarantees with this release? For instance, can I > install 1.0.0 and know that any upgrades to 1.0.x won't require any changes > on my part, and 1.1.x will only add features (and not take away - or change - > any of those I'm relying on!)? Really, I like something written down so that > developers can't break the rules ;) , like http://semver.org/ or Django's > release process[0].
That's a very good question, indeed. So far we've been working on a single branch. Features has been added and stabilized one by one, which kind of allowed as to: 1.- Release often. The release cycles have been fairly short, which is good. 2.- Release half-baked modules, and use the community feedback to finish the work. IMO, it'd be desirable to publish a roadmap with the upcoming releases and features, at the same time that we continue working on a single branch. In that way, you guys would know in advance what is going to happen (and maybe skip some version) and we could continue using this faster development model. > As I'm sure you know, while many of us like the bleeding-edge, it is really > not a good quality to have in a sysadmin, and our managers tend to prefer > stability over fancy new features as well. They do the right thing, actually. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
