Following up on this. We are two weeks away from the next release.
Bob, you mentioned on IRC that you could help me with this. What time is
convenient for you?
On 17 April 2013 16:01, Noah Slater nsla...@apache.org wrote:
I'll let someone more familiar with Git, and the conversations we had
Hey guys,
Just following up on this, as it's been five days. And I can't move ahead
without help.
At a minimum, we need to create the 1.4.x branch. But I'd really like for
us to properly document our merge procedure (which has languished because I
don't know Git well enough to fill out the
On Wed, Apr 17, 2013 at 3:45 PM, Noah Slater nsla...@apache.org wrote:
At a minimum, we need to create the 1.4.x branch. But I'd really like for
us to properly document our merge procedure (which has languished because I
don't know Git well enough to fill out the details) and then for us to
So that features can be merged into it as they become ready.
Check out:
http://wiki.apache.org/couchdb/Merge_Procedure
Thoughts?
On 17 April 2013 14:47, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Apr 17, 2013 at 3:45 PM, Noah Slater nsla...@apache.org wrote:
At a minimum, we need
On Wed, Apr 17, 2013 at 4:02 PM, Noah Slater nsla...@apache.org wrote:
So that features can be merged into it as they become ready.
Check out:
http://wiki.apache.org/couchdb/Merge_Procedure
Thoughts?
Seems like you could call the next-feature-release branch master,
and not have to start a
The goal was that you only merge in features when they are ready, and come
with tests, and docs, and what have you. And that you actually call a lazy
consensus merge request on dev@ before you can merge in.
On 17 April 2013 15:18, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Apr 17,
I'll let someone more familiar with Git, and the conversations we had
around this, answer.
To be honest, I am less interested in debating the specifics of the
proposal than I am about actually getting a proposal agreed upon, and
putting it into practice. We are a little over a week away from the
On Feb 15, 2012, at 03:22 , Brian Mitchell wrote:
Has there been any discussion around BigCouch integration strategies? It
seems like it would fit the bill for the next undertaking on the general
couch side. Does anyone from Cloudant have a suggestion for the timeline here?
Cloudant
On Feb 14, 2012, at 9:22 PM, Brian Mitchell wrote:
Has there been any discussion around BigCouch integration strategies? It
seems like it would fit the bill for the next undertaking on the general
couch side. Does anyone from Cloudant have a suggestion for the timeline here?
There's been a
On Wed, Feb 15, 2012 at 2:13 PM, Bob Dionne
dio...@dionne-associates.com wrote:
On Feb 14, 2012, at 9:22 PM, Brian Mitchell wrote:
Has there been any discussion around BigCouch integration strategies? It
seems like it would fit the bill for the next undertaking on the general
couch side.
On Wed, Feb 15, 2012 at 11:48 AM, Jan Lehnardt j...@apache.org wrote:
On Feb 15, 2012, at 03:22 , Brian Mitchell wrote:
Any other work from mobile builds and the like might be interesting to
support. Were there any interesting changes to pull in from the mobile and
embedded device ports?
That sounds really neat, a number of folks have asked for such a thing.
Right, the ddocs, validation funs, etc.. currently aren't stored globally,
which requires clustered calls to retrieve them
On Feb 15, 2012, at 8:21 AM, Benoit Chesneau wrote:
On Wed, Feb 15, 2012 at 2:13 PM, Bob Dionne
So far we have:
https://issues.apache.org/jira/browse/COUCHDB-1410
On Tue, Feb 14, 2012 at 12:16 PM, Noah Slater nsla...@tumbolia.org wrote:
Devs,
Please use this thread to discuss roadmap items for the 1.3.0 release.
The current hot topic seems to be number handling. We'd like to
Has there been any discussion around BigCouch integration strategies? It seems
like it would fit the bill for the next undertaking on the general couch side.
Does anyone from Cloudant have a suggestion for the timeline here?
Any other work from mobile builds and the like might be interesting to
On Thu, Feb 10, 2011 at 11:44 AM, Jan Lehnardt j...@apache.org wrote:
On 10 Feb 2011, at 17:29, Gabriel Farrell wrote:
On Tue, Feb 8, 2011 at 11:37 AM, Robert Newson robert.new...@gmail.com
wrote:
You're absolutely right. 1.0.2 was ready to go quite some time ago but
several bugs were
On Tue, Feb 8, 2011 at 11:37 AM, Robert Newson robert.new...@gmail.com wrote:
You're absolutely right. 1.0.2 was ready to go quite some time ago but
several bugs were found as we were releasing. We decided, as a team,
that we couldn't ship with the bugs that were found, so we elected to
fix
On 10 Feb 2011, at 17:29, Gabriel Farrell wrote:
On Tue, Feb 8, 2011 at 11:37 AM, Robert Newson robert.new...@gmail.com
wrote:
You're absolutely right. 1.0.2 was ready to go quite some time ago but
several bugs were found as we were releasing. We decided, as a team,
that we couldn't ship
Hi,
On 9 Feb 2011, at 08:29, Benoit Chesneau wrote:
It's not clear to me that couchdb would benefit by bundling
clustering and search. Lucene has an approach that might work for
us, namely where there's an explicit core project, with a number of
supplementary parts. Releases are aligned for
Hi,
- a really good plugin story (geocouch, lucene search, easy to compile
against couchdb sources)
I don't know how possible this is (I can think of a number of issues without
trying) but having these plugins uploadable into a database in a similar manner
to views would be super sweet. It
Randall Leeds wrote:
My priorities are:
- a really good embedding story (android, desktop apps, couchbase, etc ...)
...
- a really good build story (particularly android, windows)
Having recently worked with the Android port (see build instructions on
wiki -- soon to be updated
On Tue, Feb 8, 2011 at 10:02 PM, Noah Slater nsla...@apache.org wrote:
On 8 Feb 2011, at 20:53, Benoit Chesneau wrote:
What is it supposed to mean ? A roadmap is a a detailed plan to guide
progress toward a goal . Why couldn't we define goals ?
I think Jan's point is that we use the JIRA
On Tue, Feb 8, 2011 at 5:19 PM, Robert Newson robert.new...@gmail.com wrote:
We do need to improve at releases, though I think we can all agree
that 1.0.2 was just a particularly difficult one, pretty atypical.
As for roadmap, I can see a need to revisit it. I'm not sure what
should be on it,
On Tue, Feb 8, 2011 at 6:42 PM, Peter Nolan peterwno...@gmail.com wrote:
I would like a more formal direction on the future of couchapps. I am
unsure how couchapps will proceed, but one thing i would like to see is the
ability of your basic internet users to be able to form their own
On 9 Feb 2011, at 09:26, Benoit Chesneau wrote:
On Tue, Feb 8, 2011 at 10:02 PM, Noah Slater nsla...@apache.org wrote:
On 8 Feb 2011, at 20:53, Benoit Chesneau wrote:
What is it supposed to mean ? A roadmap is a a detailed plan to guide
progress toward a goal . Why couldn't we define
We should be clear that just because Jira has that helpful 'Roadmap'
panel, doesn't mean it's our official roadmap. It really isn't, though
that is how Jira would like us to do things. I can't speak for
everyone, but Jira, to me, is just a tool, it's not the boss of me.
B.
On 9 February 2011
What do you mean by official here?
On 9 Feb 2011, at 12:39, Robert Newson wrote:
We should be clear that just because Jira has that helpful 'Roadmap'
panel, doesn't mean it's our official roadmap. It really isn't, though
that is how Jira would like us to do things. I can't speak for
On Tue, Feb 8, 2011 at 10:24, Benoit Chesneau bchesn...@gmail.com wrote:
... and you ?
Most of all, I want a better schedule/insight into the release
process. Even when reading the dev list, it's completely unclear when
I might expect the next release or what the blockers are. Releases
seem to
On Tue, Feb 8, 2011 at 11:24 AM, Benoit Chesneau bchesn...@gmail.comwrote:
... and you ?
- erlang api / plugin support
- easier build process on Windows
-juhani
+1 full-text search
+1 documentation
On Tue, Feb 8, 2011 at 4:07 AM, Juhani Ränkimies juh...@juranki.com wrote:
On Tue, Feb 8, 2011 at 11:24 AM, Benoit Chesneau bchesn...@gmail.comwrote:
... and you ?
- erlang api / plugin support
- easier build process on Windows
-juhani
On Tue, Feb 8, 2011 at 10:33 AM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Tue, Feb 8, 2011 at 10:24, Benoit Chesneau bchesn...@gmail.com wrote:
... and you ?
Most of all, I want a better schedule/insight into the release
process. Even when reading the dev list, it's completely unclear
On Tue, Feb 8, 2011 at 16:57, Noah Slater nsla...@apache.org wrote:
For step 2, we follow the roadmap that is generated in JIRA. That is, the
roadmap is constantly maintained through ticket work and ticket maintenance.
A link to this is even included prominently on the project homepage. We
We do need to improve at releases, though I think we can all agree
that 1.0.2 was just a particularly difficult one, pretty atypical.
As for roadmap, I can see a need to revisit it. I'm not sure what
should be on it, I suspect everyone has their pet feature or ten to
add. So, I'm wary about
On 8 Feb 2011, at 16:08, till wrote:
IMHO a roadmap is defined by more than there's a new jira issue, we
need to fix it with the next release.
I think you're misunderstanding me. In JIRA, you can pin tickets to release
versions. This is a perfectly good way of constructing a roadmap. And if
On 8 Feb 2011, at 16:14, Dirkjan Ochtman wrote:
Still, the problem I have is that it seems like there is a tendency to
make releases large; it seems like there's little control against devs
wanting to add their one more thing. Particularly for bugfix
releases; from 1.0.1 it took almost 6
You're absolutely right. 1.0.2 was ready to go quite some time ago but
several bugs were found as we were releasing. We decided, as a team,
that we couldn't ship with the bugs that were found, so we elected to
fix them and delay the release. I think that was the right decision.
We should only
I would like a more formal direction on the future of couchapps. I am
unsure how couchapps will proceed, but one thing i would like to see is the
ability of your basic internet users to be able to form their own couchapps
by easily integrating other couchapps into their databases, modifying
I'm going to chime in here and say that improved build support for
Android would be terrific. There are already some patches available for
this and it would be nice to see them included in the official releases.
Hopefully this doesn't equate with asking for ponies.
I'd be happy to assist
On Tue, Feb 8, 2011 at 01:24, Benoit Chesneau bchesn...@gmail.com wrote:
Hi all,
With the announce of another /couchdb fork/project embedding couchdb/ I
think it's the perfect time to define ourself for next releases.
What will be CouchDB 1.2 or 2.0, what do we target, what is our
On 8 Feb 2011, at 17:32, Noah Slater wrote:
On 8 Feb 2011, at 16:14, Dirkjan Ochtman wrote:
Still, the problem I have is that it seems like there is a tendency to
make releases large; it seems like there's little control against devs
wanting to add their one more thing. Particularly for
On Tue, Feb 8, 2011 at 9:40 PM, Jan Lehnardt j...@apache.org wrote:
On 8 Feb 2011, at 17:32, Noah Slater wrote:
On 8 Feb 2011, at 16:14, Dirkjan Ochtman wrote:
Still, the problem I have is that it seems like there is a tendency to
make releases large; it seems like there's little control
On 8 Feb 2011, at 20:53, Benoit Chesneau wrote:
What is it supposed to mean ? A roadmap is a a detailed plan to guide
progress toward a goal . Why couldn't we define goals ?
I think Jan's point is that we use the JIRA roadmap as an advisory only, and
never state that we are committing to
On Tue, Feb 9, 2010 at 3:51 AM, Mark Hammond skippy.hamm...@gmail.com wrote:
On 9/02/2010 7:05 AM, Per Ejeklint wrote:
And will official windows builds be available with it?
I've been putting together the official binaries for 0.10 and will be
making some just as official for 0.11. I expect
On Sun, Nov 1, 2009 at 8:15 PM, Chris Anderson jch...@apache.org wrote:
On Sun, Nov 1, 2009 at 11:00 AM, Suhail Ahmed suhail...@gmail.com wrote:
Hi,
Any chance of seeing native erlang RPC protocol in 11 or soon there after?
This may be part of the Cloudant clustering codebase. I can't speak
On Nov 2, 2009, at 4:19 AM, Benoit Chesneau wrote:
On Sun, Nov 1, 2009 at 8:15 PM, Chris Anderson jch...@apache.org
wrote:
On Sun, Nov 1, 2009 at 11:00 AM, Suhail Ahmed suhail...@gmail.com
wrote:
Hi,
Any chance of seeing native erlang RPC protocol in 11 or soon
there after?
This may
On Mon, Nov 2, 2009 at 6:59 PM, Adam Kocoloski kocol...@apache.org wrote:
On Nov 2, 2009, at 4:19 AM, Benoit Chesneau wrote:
On Sun, Nov 1, 2009 at 8:15 PM, Chris Anderson jch...@apache.org wrote:
On Sun, Nov 1, 2009 at 11:00 AM, Suhail Ahmed suhail...@gmail.com
wrote:
Hi,
Any chance of
On Mon, Nov 2, 2009 at 7:10 PM, Benoit Chesneau bchesn...@gmail.com wrote:
About that I had done some works on rpc calls based on hovercraft.
Code is here and wasn't finished :
http://github.com/benoitc/couchdb/blob/rpc/src/couchdb/couch_rpc.erl
Reading this code I don't know why I used a
On Nov 2, 2009, at 12:56 AM, Randall Leeds wrote:
I'd like to add to see a patch to add filtering replication
processes with
an Erlang function. I think it would have lots of utility for any
clustering
solution that wants to get pushed into the trunk. I'm going to try
to write
the patch
On 1 Nov 2009, at 15:44, Benoit Chesneau wrote:
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
Hi,
Any chance of seeing native erlang RPC protocol in 11 or soon there after?
Cheers
Suhail
On Sun, Nov 1, 2009 at 6:48 PM, Chris Anderson jch...@apache.org wrote:
Thanks Benoit for the topic,
I've got a wishlist for 0.11 / 1.0 - some of it I'd be game to
implement, some of it I think
On Sun, Nov 1, 2009 at 11:00 AM, Suhail Ahmed suhail...@gmail.com wrote:
Hi,
Any chance of seeing native erlang RPC protocol in 11 or soon there after?
This may be part of the Cloudant clustering codebase. I can't speak
for them, but from what I've heard it does inter-node communication in
a
Hey Chris,
I like hovercraft and it's simple and clean api to talk to couch. Are you
talking about clustering over RPC? I know way too little about couch to
mouth off like this, working my way to defining a structure for trees and
graphs in couch is keeping me busy enough.
Cheers
Suhail
On
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
On Sun, Nov 1, 2009 at 4:55 PM, Mark Hammond skippy.hamm...@gmail.com wrote:
On 2/11/2009 9:13 AM, Paul Davis wrote:
couchjs security
...
The first step to securing cURL handlers I'm going to tackle is the
basic all-or-nothing HTTP support. With something like --with-http as
Chris
On Tue, Feb 10, 2009 at 11:46 AM, Kerr Rainey kerr.rai...@gmail.com wrote:
Is there still interest in stabilising a native erlang interface?
--
Kerr
Definitely. I was contemplating this a bit the other day. I wonder if
it wouldn't be beneficial to create a couch_api.erl and just define an
* Full Text Search interface
- We've had basically working patches for this floating around for a while.
- It seems simple enough, we just need someone who comfortable in
Java to step up to the plate and write a Lucene adapter. (Thanks!)
I'm more than happy to look at this when I get time, I've
I've made some progress on this, fwiw;
http://github.com/rnewson/couchdb-lucene
B.
On Tue, Feb 10, 2009 at 12:27 PM, Kevin Jackson foamd...@gmail.com wrote:
* Full Text Search interface
- We've had basically working patches for this floating around for a while.
- It seems simple enough, we
On Tue, Feb 10, 2009 at 8:53 AM, Paul Davis paul.joseph.da...@gmail.com wrote:
On Tue, Feb 10, 2009 at 11:46 AM, Kerr Rainey kerr.rai...@gmail.com wrote:
Is there still interest in stabilising a native erlang interface?
--
Kerr
Definitely. I was contemplating this a bit the other day. I
2009/2/10 Michael McDaniel couc...@autosys.us:
... also, an Erlang API that skips the
JSON -convert- native Erlang terms
translation overhead. Being as term translation is not necessary
when talking 'directly' with the CDB engine
(e.g. couch_query_servers:map_docs/2
On Mon, Feb 9, 2009 at 4:06 PM, Chris Anderson jch...@apache.org wrote:
Couch Devs,
From the beginning of this project, we've had a shared vision for
CouchDB. The best documentation of that vision (in my mind) has been
the text available at http://couchdb.apache.org/docs/overview.html
On Feb 9, 2009, at 4:06 PM, Chris Anderson wrote:
* Incremental Map Reduce
- This is also strong right now. It could be faster, but so far it's
been fast enough.
I'd like to see built-in reductions for simple and commonly used
things like count, sum, average, etc. When used it would
On 10/02/2009, at 9:24 AM, Damien Katz wrote:
On Feb 9, 2009, at 4:06 PM, Chris Anderson wrote:
* Incremental Map Reduce
- This is also strong right now. It could be faster, but so far it's
been fast enough.
I'd like to see built-in reductions for simple and commonly used
things like
61 matches
Mail list logo
