On Nov 1, 2009, at 4:59 PM, Jan Lehnardt wrote:
On 1 Nov 2009, at 19:48, Chris Anderson wrote:
cron / event / changes handler
Applications need to be able to trigger functionality in a periodic
or event-based way. We could probably piggyback on _changes heartbeat
to provide cron + event services. The idea is a design document
function ("event" or "cron" or maybe "trigger") that is called once
for each item in the changes feed.
This is the one I'm least sure about, but I've heard a lot of people
request it. It's problematic because cron functionality isn't that
useful unless it has side-effects, which brings the whole sandbox/
http
question up again.
We need this for 0.11 to allow continuous replication to survive
server crashes.
+1 This is pretty much the only feature I want before 1.0.0.
Everything else in this thread so far isn't important enough to hold
up 1.0.0.
In my opinion, we should focus on fixing bugs, filling in small gaps
in the APIs, better testing and optimizations.
I think we should set a hard date for Feb 1 for feature freeze for a
0.11.0 branch. The next version, 0.11.0, once stabilized, should be
considered a release candidate, followed by 1.0.0 once proven stable
in production.
Once we branch for 0.11.0, All new features will be in trunk for
2.0.0, and might be included in a later 1.1.0 release if needed.
-Damien
While we are at it, we should add means to
trigger compaction periodically or when certain limits are
reached (IIRC Adam mentioned a waste-factor for databases
to see when compaction is worth triggering). This would be
the first thing I'd start working for new features.
We also have a few open ends in the API that need
consolidation. e.g. making the show/list/update handler
more RFC2616 aware (sending Location e.g.). There's a
few more of these. We should probably work on them before
working on new half-baked features :)
--
Furthermore, more etap tests and a benchmarking suite
would be great.
Cheers
Jan
--
rewriter
There's getting to be a pretty common pattern where people write
CouchApps and then deploy them behind a rewrite proxy. We've already
got rewrite patches floating around. It's just a matter of making the
API decisions.
clustering
I've heard Cloudant has some clustering code, I'd definitely be
willing to help with integration, and I'm sure there are other people
who would as well.
Cheers,
Chris
On Sun, Nov 1, 2009 at 7:02 AM, Benoit Chesneau
<[email protected]> wrote:
was sent on user@ sorry for crossposting .
---------- Forwarded message ----------
From: Benoit Chesneau <[email protected]>
Date: Sun, Nov 1, 2009 at 3:44 PM
Subject: roadmap 0.11/1.0
To: [email protected]
Hi all,
http://couchdb.apache.org/roadmap.html hasn't been updated. And in
fact i'm really curious. What is the next things on the roadmap ?
Also
damien spoke in june to have a fixed release schedule (one every 6
months ?) is it still something in view ?
- benoit
--
Chris Anderson
http://jchrisa.net
http://couch.io
