Re: [DISCUSS] CouchDB Roadmap

one, > > this is one of the threads we promised. This one covers the roadmap > discussion. > > This thread aims to answer: > > - which version would the FDB work land in? > - what happens with non-FDB CouchDB until then? > - specifically, how are the current roadmap items

Re: [DISCUSS] CouchDB Roadmap

in 1504 add up to much less than a redesign. B. > On 25 Jan 2019, at 11:56, Jan Lehnardt wrote: > > Hi everyone, > > this is one of the threads we promised. This one covers the roadmap > discussion. > > This thread aims to answer: > > - which version would

[DISCUSS] CouchDB Roadmap

Hi everyone, this is one of the threads we promised. This one covers the roadmap discussion. This thread aims to answer: - which version would the FDB work land in? - what happens with non-FDB CouchDB until then? - specifically, how are the current roadmap items affected? - how are the two

CouchDB Roadmap uploaded into GitHub Issues

Hi everyone, >From the last CouchDB Summit (February 2017), 42 issues have been entered into GitHub describing the foreseeable future of CouchDB. The list included some items which have already been completed, like CI and packaging work, pluggable storage engines, and Fauxton information density

Re: CouchDB 1.7.0 Roadmap

Hi Johs, Yes, I confirm that proxy feature is already working for us. --Giovanni 2015-11-13 8:29 GMT+01:00 Johs Ensby : > Giovanni, > you said earlier in a conversation about proxy > > > On 21. okt. 2015, at 17.23, Giovanni Lenzi

Re: CouchDB 1.7.0 Roadmap

Hi awesome CouchDB folks, my friend Peter and I would very much enjoy evaluating the mentioned auth topics, JWT is especially intriguing to us. > May be we can also include else experimental features, like JWT and/or > Delegated auth. Personally, I would like to see them, but it's all up > to

Re: CouchDB 1.7.0 Roadmap

Giovanni, you said earlier in a conversation about proxy > On 21. okt. 2015, at 17.23, Giovanni Lenzi > wrote: > I think CouchDB already has a forward proxy feature for #1 use case > (http://docs.couchdb.org/en/1.6.1/config/proxying.html >

Re: CouchDB 1.7.0 Roadmap

f-topic > > Thanks for your roadmap to 1.7.0.. seems very very juicy! > > About the "COUCHDB-2752: Validate Host header" in your list. As > documented here (https://issues.apache.org/jira/browse/COUCHDB-2752), to > me it seems that flag can perfectly be used in the pr

Re: CouchDB 1.7.0 Roadmap

On Thu, Nov 12, 2015 at 6:54 PM, Giovanni Lenzi <g.le...@smileupps.com> wrote: > I'm writing you privately because I don't want the main thread to go > off-topic Well, no (: > Thanks for your roadmap to 1.7.0.. seems very very juicy! > > About the "COUCHDB-2752: Val

CouchDB 1.7.0 Roadmap

Dear CouchDB team, While we're all working on 2.0 is in progress, I fear that we'll end this year without a single release. Technically, there is only one month left till 2016 excluding holidays, but let's be honest - that's not enough for 2.0. So I propose the plan for 1.7 release to not end

Re: CouchDB 1.7.0 Roadmap

Hi Alexander, I'm writing you privately because I don't want the main thread to go off-topic Thanks for your roadmap to 1.7.0.. seems very very juicy! About the "COUCHDB-2752: Validate Host header" in your list. As documented here (https://issues.apache.org/jira/browse/COUCHDB-27

Re: CouchDB 1.7.0 Roadmap

On Thu, Nov 12, 2015 at 7:20 PM, Tomas Novysedlak wrote: > > Just a quick one. How about long promised > https://issues.apache.org/jira/browse/COUCHDB-1415 ? I'll take a look, but no promises. I'm also not quite sure which exact changes fixed this for 2.0 and will

Re: CouchDB 1.7.0 Roadmap

Hi Alexander, Just a quick one. How about long promised https://issues.apache.org/jira/browse/COUCHDB-1415 ? Thank you, Tomas On Thu, Nov 12, 2015 at 4:05 PM, Alexander Shorin wrote: > Dear CouchDB team, > > While we're all working on 2.0 is in progress, I fear that

Re: Roadmap process and merge procedure

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

Re: Roadmap process and merge procedure

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

Re: Roadmap process and merge procedure

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

Re: Roadmap process and merge procedure

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

Re: Roadmap process and merge procedure

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

Re: Roadmap process and merge procedure

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,

Re: Roadmap process and merge procedure

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

Roadmap process and merge procedure

Devs, With 1.3.0 out, it is time we revisit these docs: http://wiki.apache.org/couchdb/Roadmap_Process http://wiki.apache.org/couchdb/Merge_Procedure Our next bugfix release target is 1st May. Our next feature release target is 1st July. What do we need to do *now* to prepare for

Re: [PROPOSAL] Official roadmap, and merge procedure

wrote: On Jun 16, 2012, at 18:45 , Noah Slater wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship

Re: [PROPOSAL] Official roadmap, and merge procedure

bump. On Mon, Jun 18, 2012 at 10:29 AM, Benoit Chesneau bchesn...@gmail.com wrote: On Sat, Jun 16, 2012 at 6:45 PM, Noah Slater nsla...@tumbolia.org wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like

Re: [PROPOSAL] Official roadmap, and merge procedure

On Sat, Jun 16, 2012 at 6:45 PM, Noah Slater nsla...@tumbolia.org wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want

Re: [PROPOSAL] Official roadmap, and merge procedure

Heya, I'm in favour of the proposal. I recognise that there are a few things that need to be refined, but I think what we have is good enough to get going and refine as we go along. With QA for example, it is up to the release master to judge whether a release is good to go. If the community QA

Re: [PROPOSAL] Official roadmap, and merge procedure

On Jun 16, 2012, at 18:45 , Noah Slater wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship something

Re: [PROPOSAL] Official roadmap, and merge procedure

, at 18:45 , Noah Slater wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship something, you have

Re: [PROPOSAL] Official roadmap, and merge procedure

wrote: On Jun 16, 2012, at 18:45 , Noah Slater wrote: Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship

[PROPOSAL] Official roadmap, and merge procedure

Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship something, you have to submit a merge request to an active release

Re: [PROPOSAL] Official roadmap, and merge procedure

On Sat, Jun 16, 2012 at 6:45 PM, Noah Slater nsla...@tumbolia.org wrote: 1. We'd like to proposed formal time-based releases Love it. In fact, I think I proposed it before. I think this will be a much better way of making CouchDB administration easy. Details of these proposals can be found

Re: [PROPOSAL] Official roadmap, and merge procedure

This is an excellent idea, more predictability is always a Good Thing, regardless of how big each release is. Being able to schedule downtime for upgrades on a predictable schedule is a massive tick. Martin Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Saturday, 16 June 2012 at

Re: [PROPOSAL] Official roadmap, and merge procedure

On 16 June 2012 17:45, Noah Slater nsla...@tumbolia.org wrote: 1. We'd like to proposed formal time-based releases http://wiki.apache.org/couchdb/Roadmap_Process This is a big improvement, but... :) If the QA is good enough, it would be a little better to have feature releases every month

Re: Roadmap for the 1.3.0 release

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

Re: Roadmap for the 1.3.0 release

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

Re: Roadmap for the 1.3.0 release

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.

Re: Roadmap for the 1.3.0 release

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?

Re: Roadmap for the 1.3.0 release

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

Roadmap for the 1.3.0 release

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 formalise, improve, and document how we handle numbers. What else? Thanks, N

Re: Roadmap for the 1.3.0 release

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

Re: Roadmap for the 1.3.0 release

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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 12

Re: roadmap

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 everyone

roadmap

roadmap? What will be the next couchdb? For me: - Plugin support - improved CouchApp engine - Improve possibilities to integrate CouchDB in other projects - Clean API, so couchdb features can be called more easily in other erlang programs or plugins Other feature I wish: - Official Apache

Re: roadmap

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

Re: roadmap

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

Re: roadmap

+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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

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

Re: roadmap

. There are other reasons for that of course. So can we try to define this time a good old roadmap? What will be the next couchdb? For me: - Plugin support - improved CouchApp engine - Improve possibilities to integrate CouchDB in other projects - Clean API, so couchdb features can be called more

Re: roadmap

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

Re: roadmap

that. Cheers Jan -- 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 ? - benoît

Re: roadmap

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

Re: Auth Roadmap

On Fri, Feb 12, 2010 at 7:10 AM, Chris Anderson jch...@apache.org wrote: On Tue, Feb 9, 2010 at 2:52 PM, Chris Anderson jch...@apache.org wrote: Devs, I've been getting a lot of feedback about the authentication authorization work that I did over the holidays and over the last few weeks.

Re: Auth Roadmap

Benoit, The .ini file suggestion seems a good idea, as it allows for pluggable password hash validation. Now we're thinking about OpenLDAP schemes, but tomorrow someone might suggest or require something else. About the JSON object, containing the hash scheme in an attribute and the hash in a

Re: Auth Roadmap

I think what you say has merit, but it doesn't jibe with my understanding of our implementation in a logical way. I'm ready to ship the basic programming model we have - it maps cleanly onto the underlying infrastructure (less abstraction can be a good thing). With respect, I think we're

Re: Auth Roadmap

On Thu, Feb 11, 2010 at 4:20 AM, Brian Candler b.cand...@pobox.com wrote: I think what you say has merit, but it doesn't jibe with my understanding of our implementation in a logical way. I'm ready to ship the basic programming model we have - it maps cleanly onto the underlying infrastructure

Re: Auth Roadmap

On Thu, Feb 11, 2010 at 08:32:49AM -0800, Chris Anderson wrote: To be clear, I'm not suggesting this at all. It'd be more like (pardon my earlier accidental _underscores): { readers:{ names:[foo,bar], roles:[baz, _replicator, doctor] }, admins:{

Re: Auth Roadmap

On Tue, Feb 9, 2010 at 2:52 PM, Chris Anderson jch...@apache.org wrote: Devs, I've been getting a lot of feedback about the authentication authorization work that I did over the holidays and over the last few weeks. There are also some enhancements I've been thinking about for a while.

Re: Auth Roadmap

On 11 Feb 2010, at 22:10, Chris Anderson wrote: 2) ACLs / Security Object I couldn't originally think of a reason the validation funs would need to see the per-db admins / readers lists. Brian has a use case for this. Also, I think I can accomplish this feature while also simplifying the

Re: Auth Roadmap

On Wed, Feb 10, 2010 at 12:24:26AM +0100, Benoit Chesneau wrote: I've read all the thread, and I'm not conviced all readers and admins should be in one doc. List could be long also it would require to check if one already exists some stuff like it. Why not putting all in their docs and making

Re: Auth Roadmap

On Wed, Feb 10, 2010 at 2:12 AM, Brian Candler b.cand...@pobox.com wrote: On Wed, Feb 10, 2010 at 12:24:26AM +0100, Benoit Chesneau wrote: I've read all the thread, and I'm not conviced all readers and admins should be in one doc. List could be long also it would require to check if one

Re: Auth Roadmap

On Wed, Feb 10, 2010 at 2:27 PM, Brian Candler b.cand...@pobox.com wrote: On Wed, Feb 10, 2010 at 07:26:00AM -0800, Chris Anderson wrote: The problem with this approach, imho, is that currently users have the same set of roles in every db. That is, your userCtx doesn't change depending on the

Re: Roadmap 0.11?

to have a roadmap published. It's definitely needed for non developers people that want to have an idea of futures developments and orientation. - benoît

Auth Roadmap

Devs, I've been getting a lot of feedback about the authentication authorization work that I did over the holidays and over the last few weeks. There are also some enhancements I've been thinking about for a while. Here's a quick list of what I see as the important things to do. I'm not

Roadmap 0.11?

Jan asked me to take this in dev@ so here I am. :-) The official roadmap page (http://couchdb.apache.org/roadmap.html) is a tiiiny little outdated. As I'm trying to convince my new customer to make an epic technology leap I need as much info as possible about the near future for CouchDB. 0.11

Re: Updating the CouchDB roadmap

On Sun, Jan 24, 2010 at 09:33:02PM -0800, Chris Anderson wrote: To round out this list, I think * Reader ACLs ... look like they will make it into 0.11. That's the jchris/readeracl branch presumably? I was hoping to turn my counter-proposal(*) into code, but I've not had any time to do so

Re: Updating the CouchDB roadmap

On Mon, Jan 25, 2010 at 1:14 AM, Brian Candler b.cand...@pobox.com wrote: On Sun, Jan 24, 2010 at 09:33:02PM -0800, Chris Anderson wrote: To round out this list, I think * Reader ACLs ... look like they will make it into 0.11. That's the jchris/readeracl branch presumably? I was hoping

Re: Updating the CouchDB roadmap

Thanks for reminding me that I should set _all_dbs to hide dbs the curertn user can't read if that doesn't incur much additional overhead. I think that it will incur a huge overhead, if there are a large number of databases and the reader rights are stored within the databases themselves.

Re: Updating the CouchDB roadmap

On Fri, Dec 18, 2009 at 20:30, Damien Katz dam...@apache.org wrote: I think we should set a hard date of Feb 1. for feature freeze, 0.11.0 is the last new feature release. Did this ever turn into some kind of consensus, or is there no idea yet about a 0.11 release time frame? Cheers, Dirkjan

Re: Updating the CouchDB roadmap

On Thu, Dec 3, 2009 at 8:29 PM, Noah Slater nsla...@tumbolia.org wrote: Hey, As part of the release procedure, this is a request to update the roadmap document:        http://couchdb.apache.org/roadmap.html Please comment on what should be added, and what should be removed. After a we

Re: Updating the CouchDB roadmap

An updated (and no longer breaking 4 test cases) patch for storing compressed attachments was added to tickets 583 and 437. cheers On Sat, Dec 19, 2009 at 8:46 AM, Filipe David Manana fdman...@gmail.comwrote: After rev 891077 (ticket 558, md5 integrity check) I need to update that patch for

Re: Updating the CouchDB roadmap

On Sat, Dec 19, 2009 at 9:08 AM, Chris Anderson jch...@apache.org wrote: On Fri, Dec 18, 2009 at 9:02 AM, Noah Slater nsla...@tumbolia.org wrote: On 18 Dec 2009, at 16:45, Dirkjan Ochtman wrote: That said, it's perfectly alright if there's no roadmap at all, I'm just surprised by the lack

Re: Updating the CouchDB roadmap

would I tell everyone else that I expect you to write a given feature? Granted, I would be perfectly happy referring to versions by sha1 so maybe I'm a bit crazy. HTH, Paul Davis Well roadmap in a sense would allow everyone to know who working on what. Or if not who, what is the work

Re: Updating the CouchDB roadmap

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

Re: Updating the CouchDB roadmap

On Fri, Dec 18, 2009 at 2:39 AM, Dirkjan Ochtman djc.ocht...@gmail.com 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?

Re: Updating the CouchDB roadmap

Hey, Does JIRA have a page what we could use as the roadmap? That would have the added advantage of updating itself automatically as we edited tickets. I found the roadmap tab from the main CouchDB page, but it doesn't have any tickets for post 0.10 on it. Thoughts? Thanks, Noah

Re: Updating the CouchDB roadmap

Link might be handy: http://forrest.apache.org/forrest-issues.html On Fri, Dec 18, 2009 at 12:09 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Fri, Dec 18, 2009 at 12:05 PM, Noah Slater nsla...@tumbolia.org wrote: Hey, Does JIRA have a page what we could use as the roadmap

Re: Updating the CouchDB roadmap

Jira does build a roadmap for you, but it depends on you filing bugs/tasks and assigning them as fix for version. I'm not sure we all can add new versions (that should be locked down if it's not already), but that's how roadmaps are handled in jira. B. On Fri, Dec 18, 2009 at 5:10 PM, Paul Davis

Re: Updating the CouchDB roadmap

On 18 Dec 2009, at 17:37, Robert Newson wrote: Jira does build a roadmap for you, but it depends on you filing bugs/tasks and assigning them as fix for version. I'm not sure we all can add new versions (that should be locked down if it's not already), but that's how roadmaps are handled

Re: Updating the CouchDB roadmap

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

Re: Updating the CouchDB roadmap

FYI, I haven't looked at this patch's code, but I like it's concepts and I hope of the other committers will have a chance to look at it soon and work out any issues to get it checked into trunk. If not I eventually will get around to it, but I can't promise when. -Damien On Dec 9, 2009, at

Re: Updating the CouchDB roadmap

After rev 891077 (ticket 558, md5 integrity check) I need to update that patch for storing gzip compressed attachments. The md5 calculated by couch_stream corresponds to the md5 of the gzipped content, therefore not matching the attachment content sent by the client for those attachments having a

Re: Updating the CouchDB roadmap

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

Re: Updating the CouchDB roadmap

On Thu, Dec 3, 2009 at 8:29 PM, Noah Slater nsla...@tumbolia.org wrote: Hey, As part of the release procedure, this is a request to update the roadmap document:        http://couchdb.apache.org/roadmap.html Please comment on what should be added, and what should be removed. for next

  1   2   >