Good luck!cheers
Mahesh Paolini-Subramanya | CTO |mah...@aptela.com|703.386.1500 Ext. 91002250 Corporate Park Drive | Suite 150| Herndon, VA |www.aptela.comCheck out ourBlog|Follow us onTwitter|Refer aFriend
On Feb 8, 2011, at 2:41 AM, Dirkjan Ochtman wrote:Congratulations to all of you!On Tue,
On Tue, Feb 8, 2011 at 7:41 AM, Jan Lehnardt j...@apache.org wrote:
Dear CouchDB folks, developers, users,
I don't usually post business-y things here, but I think this one warrants an
email.
I'm excited to announce that CouchOne, the company Damien, J Chris and I
founded in late 2009, is
[
https://issues.apache.org/jira/browse/COUCHDB-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991847#comment-12991847
]
Dave Cottlehuber commented on COUCHDB-963:
--
Also replicated, EC2 large instance,
[
https://issues.apache.org/jira/browse/COUCHDB-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Cottlehuber updated COUCHDB-963:
-
Attachment: dch_couch.log
couch log from DaveCottlehuber
Erlang processes crash when
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
timeline. What is the CouchDB core that will be used by other projects
basically.
[
https://issues.apache.org/jira/browse/COUCHDB-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991852#comment-12991852
]
Dave Cottlehuber commented on COUCHDB-963:
--
Last note for the night - there *is*
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
[
https://issues.apache.org/jira/browse/COUCHDB-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991951#comment-12991951
]
Bob Clary commented on COUCHDB-926:
---
While the situation in 1.0.2 is much improved over
+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
Hello,
you can directly work on ${COUCHDB}\share\couchdb\www to develop your
features, the couchdb http server will reflect your changes, but the merging
will of course be complicated.
Perhaps you can ask Mikeal that started to recode futon from scratch using
sammy.js (
On Feb 7, 2011, at 11:41 PM, Dirkjan Ochtman wrote:
Congratulations to all of you!
On Tue, Feb 8, 2011 at 07:41, Jan Lehnardt j...@apache.org wrote:
Instead of dwelling on the merger or technology, I'd like to address likely
questions about the relationship between Couchbase and Apache
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
Nathan,
I'll clarify what I can for the bits I know about. One important part
of Bigcouch is to be API compatible with couchdb. Obviously there are
some places where this must break down (say, controlling sharding and
r/w/n consistency) but to a large degree, we succeed at that. It's
also
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 8 Feb 2011, at 19:26, Paul Davis wrote:
A few months ago, I read about BigCouch:
BigCouch = (CouchDB + Amazon Dynamo clustering theory)
That sounds neat, and I was getting the impression this was done in Erlang
in such a way it could become part of core and was excited for it.
It
Ah, ok. I think it was mostly this in the press FAQ that confused me:
How will your technologies and products be integrated?
We plan to roll out the blended product line in several stages over the next
few months.
What I'm hearing is this Couchbase blended product is more or less a line of
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
Help appreciated.
He raises a good point though, as those links don't work now.
I'm not sure what level of description they require.
Probably nothing more than a handful of paragraphs to explain how CouchDB is a
special use-case for HTTP. In the original submission for TCP 5984, I pointed
out
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
1.0.1 sends malformed reply to some POST and GETs
-
Key: COUCHDB-1062
URL: https://issues.apache.org/jira/browse/COUCHDB-1062
Project: CouchDB
Issue Type: Bug
Components: HTTP
29 matches
Mail list logo
