Apologies for not replying, I have a lot of stuff going on right. For 1.0 features, I only want a few more enhancements to continuous replication (they might already be there) and full windows support.
I think we should set a hard date of Feb 1. for feature freeze, 0.11.0 is the last new feature release. Then after that, all new code is for stabilization until we hit 1.0. There will be exceptions some features, and we'll vote on them as they come up. But generally the rules should be post-0.11.0, no new features. 1.0 isn't the end of the line for your desired features though, While 1.0.x is for bug fixes , 1.1, 1.2 etc can have new stuff after a beta period, etc. That's my take on the roadmap. -Damien On Dec 18, 2009, at 7:58 AM, Robert Dionne wrote: > I sort of agree with you, but in all fairness some of the core programmers > have weighed in. > > To repeat my earlier post, I think it's a good time to put some stakes in the > ground with respect to direction. I'm sure there are a number of parties > interested in extending and making use of the internals and a lot has been > discussed in terms of what could be done. A roadmap would be nice, especially > since there is growing corporate support, a key selling point for CouchDB. > > > > > On Dec 18, 2009, at 2:39 AM, Dirkjan Ochtman wrote: > >> It seems weird that none of the core developers have bothered to write >> up some of their ideas here, for ten days running now. I understand >> you're all busy with Relaxed, but it doesn't have to take so long, >> does it? IMO it would be nice to have some kind of idea of where >> CouchDB is going and/or what will be in the next release. >> >> Cheers, >> >> Dirkjan >
