On Mon, Jun 1, 2009 at 3:32 PM, Paul Davis wrote:
>> "You have
> a week to notify us of a commit you think should make it into the
> upcoming maintenance release".
I think we should do that for 0.9.2.
0.9.1 has been sitting there ready to go for some time, we should get
put it through the releas
On Mon, Jun 1, 2009 at 5:24 PM, Jan Lehnardt wrote:
>
> On 1 Jun 2009, at 21:41, Paul Davis wrote:
>>
>> […] Even something like, "submit it to the user@ for an
>> informal vote" before putting in maintenance would be good enough for
>> me.
>
> For the record, user@ is not the place to do any kind
On 1 Jun 2009, at 21:41, Paul Davis wrote:
[…] Even something like, "submit it to the user@ for an
informal vote" before putting in maintenance would be good enough for
me.
For the record, user@ is not the place to do any kind of votes. dev@ is.
user@ is only provided as a convenience for Cou
[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715256#action_12715256
]
Jerry Sievert commented on COUCHDB-204:
---
thanks damien - that jives with the error m
[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715228#action_12715228
]
Damien Katz commented on COUCHDB-204:
-
Here is a discussion about someone having the s
On Mon, Jun 1, 2009 at 3:55 PM, Damien Katz wrote:
>
> On Jun 1, 2009, at 3:41 PM, Paul Davis wrote:
>
>> On Mon, Jun 1, 2009 at 3:26 PM, Damien Katz wrote:
>>>
>>> On Jun 1, 2009, at 3:00 PM, Chris Anderson wrote:
>>>
Devs,
We've talked some about discontinuing use of svn's merge/
[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715223#action_12715223
]
Damien Katz commented on COUCHDB-204:
-
It looks like all we need is a special flag pas
On Jun 1, 2009, at 3:41 PM, Paul Davis wrote:
On Mon, Jun 1, 2009 at 3:26 PM, Damien Katz wrote:
On Jun 1, 2009, at 3:00 PM, Chris Anderson wrote:
Devs,
We've talked some about discontinuing use of svn's merge/block
procedure for maintaining old release branches, in favor just asking
comm
On Mon, Jun 1, 2009 at 3:26 PM, Damien Katz wrote:
>
> On Jun 1, 2009, at 3:00 PM, Chris Anderson wrote:
>
>> Devs,
>>
>> We've talked some about discontinuing use of svn's merge/block
>> procedure for maintaining old release branches, in favor just asking
>> committers to remember to put applicab
[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715218#action_12715218
]
Chris Anderson commented on COUCHDB-204:
Thanks that'd be helpful, maybe I can mak
On Mon, Jun 1, 2009 at 12:27 PM, Paul Davis wrote:
> I know it was auto generated, but you probably should've taken the
> time to list Jan as a reason for hearing about CouchDB so we could
> finally quantify that. XD
>
Yeh seriously. There wasn't even a place to mess with the survey --
it's just
I know it was auto generated, but you probably should've taken the
time to list Jan as a reason for hearing about CouchDB so we could
finally quantify that. XD
On Mon, Jun 1, 2009 at 3:23 PM, Chris Anderson wrote:
> On Mon, Jun 1, 2009 at 12:10 PM, Chris Anderson wrote:
>> Hey everyone,
>>
>> We
On Jun 1, 2009, at 3:00 PM, Chris Anderson wrote:
Devs,
We've talked some about discontinuing use of svn's merge/block
procedure for maintaining old release branches, in favor just asking
committers to remember to put applicable patches into the 0.9.x
branch.
My experience is that by default
On Mon, Jun 1, 2009 at 3:14 PM, Chris Anderson wrote:
> On Mon, Jun 1, 2009 at 12:08 PM, Paul Davis
> wrote:
>> On Mon, Jun 1, 2009 at 3:00 PM, Chris Anderson wrote:
>>> Devs,
>>>
>>> We've talked some about discontinuing use of svn's merge/block
>>> procedure for maintaining old release branch
On Mon, Jun 1, 2009 at 12:10 PM, Chris Anderson wrote:
> Hey everyone,
>
> We thought it would be fun to hear from CouchDB users. Please take
> five minutes to fill out this survey.
>
> http://survey.io/survey/19744
>
> The survey is automatically generated, so it's a bunch of really basic
> quest
[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715209#action_12715209
]
Jerry Sievert commented on COUCHDB-204:
---
Chris,
I would be happy to show this to yo
On Mon, Jun 1, 2009 at 12:08 PM, Paul Davis wrote:
> On Mon, Jun 1, 2009 at 3:00 PM, Chris Anderson wrote:
>> Devs,
>>
>> We've talked some about discontinuing use of svn's merge/block
>> procedure for maintaining old release branches, in favor just asking
>> committers to remember to put applica
On 1 Jun 2009, at 20:49, Chris Anderson wrote:
I think 0.9.1 is ready for release.
What do you think?
+1
Jan
--
On 1 Jun 2009, at 21:00, Chris Anderson wrote:
Devs,
We've talked some about discontinuing use of svn's merge/block
procedure for maintaining old release branches, in favor just asking
committers to remember to put applicable patches into the 0.9.x
branch.
There is discussion to be had about
I think we should get the ball rolling. I can't say for certain that
the current 0.9.x has everything that it should have, though.
Adam
On Jun 1, 2009, at 3:09 PM, Paul Davis wrote:
+1
On Mon, Jun 1, 2009 at 2:49 PM, Chris Anderson
wrote:
I think 0.9.1 is ready for release.
What do yo
Hey everyone,
We thought it would be fun to hear from CouchDB users. Please take
five minutes to fill out this survey.
http://survey.io/survey/19744
The survey is automatically generated, so it's a bunch of really basic
questions, but it's the sort of thing we don't normally ask, so I bet
we can
+1
On Mon, Jun 1, 2009 at 2:49 PM, Chris Anderson wrote:
> I think 0.9.1 is ready for release.
>
> What do you think?
>
> --
> Chris Anderson
> http://jchrisa.net
> http://couch.io
>
On Mon, Jun 1, 2009 at 3:00 PM, Chris Anderson wrote:
> Devs,
>
> We've talked some about discontinuing use of svn's merge/block
> procedure for maintaining old release branches, in favor just asking
> committers to remember to put applicable patches into the 0.9.x
> branch.
>
> There is discussio
Devs,
We've talked some about discontinuing use of svn's merge/block
procedure for maintaining old release branches, in favor just asking
committers to remember to put applicable patches into the 0.9.x
branch.
There is discussion to be had about what patches are applicable to
point release branch
I think 0.9.1 is ready for release.
What do you think?
--
Chris Anderson
http://jchrisa.net
http://couch.io
On Mon, Jun 1, 2009 at 10:55 AM, Nick Gerakines wrote:
> For what it's worth, that convention is being carried over from my
> Perl history and the actual directory name is completely immaterial.
Sounds like reason enough to change it ;)
> It should be noted that the etap library does assume that
For what it's worth, that convention is being carried over from my
Perl history and the actual directory name is completely immaterial.
It should be noted that the etap library does assume that source files
and beam files exist in the src and ebin directories and they are
referenced and used when b
Chris Anderson wrote:
The next step on the roadmap is to give the ability to filter the
comet notifications with a JavaScript function. This code should not
be too hard to write but I doubt I'll have time to get to it this
week. There are a few other people who are capable of adding the
function,
On Mon, Jun 1, 2009 at 2:29 AM, Kevin Jackson wrote:
> Hi,
>> If you're feeling saucy you can also generate coverage reports like such:
>>
>> $ ERLC_FLAGS=+debug_info ./configure && make cover
>>
>> This will create a directory ./cover/ that contains an index.html that
>> will point you at all
On Mon, Jun 01, 2009 at 07:14:15AM +0100, Kevin Jackson wrote:
> > The t/* directory was just me following what I've seen as standard for
> > the etap layout so renaming it is perfectly fine with me.
>
> The etap documentation suggests t/* so that was following the guidelines.
Thanks for the clari
30 matches
Mail list logo
