Hi everybody,
I have a couple more tests to make on ensuring the timezone bug in
earlier OTP releases is correctly resolved, but the bulk of the work
is done. Unless somebody reports an issue, I'll include this branch in
master in the next week, probably cherry-picked.
[jira]:
On 31 March 2013 00:03, Benoit Chesneau bchesn...@gmail.com wrote:
I will stop here the effort in porting couchjs to this new platform. I
think i'm done with spidermonkey for awhile. Will rather port my
effort on something based on v8 and other languages alternatives:
dart and lua are good
Dear community,
This is a request to prepare binaries for the 1.3.0-rc.3 release.
Please follow the release procedure:
http://wiki.apache.org/couchdb/Release_Procedure#Preparing_the_Binary_Packages
Everyone is welcome to prepare binaries for this release.
Thanks,
--
NS
Author: nslater
Date: Sun Mar 31 14:22:45 2013
New Revision: 1692
Log:
Add 1.3.0-rc.3 release notes dir
Added:
dev/couchdb/notes/1.3.0/
dev/couchdb/notes/1.3.0/rc.3/
Author: nslater
Date: Sun Mar 31 15:04:21 2013
New Revision: 1693
Log:
Add 1.3.0-rc.3 release notes
Added:
dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html
Added: dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html
Thanks Dave!
On 31 March 2013 14:29, Dave Cottlehuber d...@jsonified.com wrote:
Hi everybody,
I have a couple more tests to make on ensuring the timezone bug in
earlier OTP releases is correctly resolved, but the bulk of the work
is done. Unless somebody reports an issue, I'll include this
I'm probably missing something here, but why can't we land BigCouch in a
single dual-release?
Timeline:
* BigCouch lands on master
* No date — it happens when it happens
* We simultaneously release 2.0.0 and 1.X.0
* This happens at the next available regular release date
* There's _no_ reason, that I can see, that this deprecation has _to
happen_ 3 months prior.
On 31 March 2013 17:40, Noah Slater nsla...@apache.org wrote:
I'm probably missing something here, but why can't we land BigCouch in a
single dual-release?
Timeline:
* BigCouch lands on master
On Mar 31, 2013, at 18:41 , Noah Slater nsla...@apache.org wrote:
* There's _no_ reason, that I can see, that this deprecation has _to
happen_ 3 months prior.
Yeah, that works too, it is the same procedure, just compressed some
more. I don’t think we intended anything special with an
From an organisational point of view, it seems much more simple to me to do
this simultaneous deprecate bits in the 1.x line while starting a new 2.x
line thing. The bit I don't know is whether this makes sense from a
technical point of view. Your plan, for instance, spaces out the API
changes and
Actually. Sorry. Let me reconsider that actually.
I think the important thing I am getting at is that if we can do the API
changes and the BigCouch merge at the same time, then we have two important
releases to do:
* 1.x line with the depreciation warnings
* 2.x line with the new stuff
* Uh, _ deprecation_ warnings. ;)
On 31 March 2013 18:06, Noah Slater nsla...@apache.org wrote:
Actually. Sorry. Let me reconsider that actually.
I think the important thing I am getting at is that if we can do the API
changes and the BigCouch merge at the same time, then we have two
Dear community,
This is a request to help with the release notes for the 1.3.0-rc.3 release.
You can view my initial draft here:
https://dist.apache.org/repos/dist/dev/couchdb/notes/1.3.0/rc.3
Please read through this and suggest any changes. The summaries were taken
from the CHANGES file.
Updated Branches:
refs/heads/master 100a46dd6 - 146370df7
Update release notes email and template
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/146370df
Tree:
Author: nslater
Date: Sun Mar 31 17:23:28 2013
New Revision: 1697
Log:
Change mime-type
Modified:
dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html (props changed)
Propchange: dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html
Author: nslater
Date: Sun Mar 31 17:28:42 2013
New Revision: 1698
Log:
Changed major release to feature release
Modified:
dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html
Modified: dev/couchdb/notes/1.3.0/rc.3/apache-couchdb-1.3.0.html
On Mar 31, 2013, at 19:06 , Noah Slater nsla...@apache.org wrote:
Actually. Sorry. Let me reconsider that actually.
I think the important thing I am getting at is that if we can do the API
changes and the BigCouch merge at the same time, then we have two important
releases to do:
*
I understand what you are saying, and I agree with it.
But the API only release seems unnecessary to me. If the version numbers
are not important (and they are not) then let's just treat them that way
and ship BigCouch in 2.0.0. Actually going out of our way to make a bunch
of (otherwise
On Mar 30, 2013, at 20:44 , Benoit Chesneau bchesn...@gmail.com wrote:
On Sat, Mar 30, 2013 at 8:29 PM, Jan Lehnardt j...@apache.org wrote:
Hi all,
It is time to think about how to square the upcoming changes to CouchDB and
the next releases.
Robert Newson and I hashed out this plan:
On Mar 31, 2013, at 20:06 , Noah Slater nsla...@apache.org wrote:
I understand what you are saying, and I agree with it.
But the API only release seems unnecessary to me. If the version numbers
are not important (and they are not) then let's just treat them that way
and ship BigCouch in
If the BigCouch merge is ready for the next feature release date, then I
would probably need a little more convincing if the proposal was to delay
it by 3 months so that we could cut 2.0.0 to make a point about version
numbers. If BigCouch is not ready by the next feature release date, then I
have
On Mar 31, 2013, at 20:10 , Noah Slater nsla...@apache.org wrote:
If the BigCouch merge is ready for the next feature release date, then I
would probably need a little more convincing if the proposal was to delay
it by 3 months so that we could cut 2.0.0 to make a point about version
[
https://issues.apache.org/jira/browse/COUCHDB-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618415#comment-13618415
]
Nick North commented on COUCHDB-1738:
-
Ability to set the UUID algorithm separately
On Sat, Mar 30, 2013 at 8:29 PM, Jan Lehnardt j...@apache.org wrote:
Bikeshed away! :)
Will there be discussion on API changes for BigCouch stuff? I don't
really have a clue on how BigCouch is different from CouchDB exactly,
all I know is it does some clustering and that's why some things are
On Mar 31, 2013, at 21:32 , Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Sat, Mar 30, 2013 at 8:29 PM, Jan Lehnardt j...@apache.org wrote:
Bikeshed away! :)
Will there be discussion on API changes for BigCouch stuff? I don't
really have a clue on how BigCouch is different from CouchDB
On Sun, Mar 31, 2013 at 9:42 PM, Jan Lehnardt j...@apache.org wrote:
We will be collecting things here:
https://issues.apache.org/jira/browse/COUCHDB-1756
There is an (incomplete) list of differences down on:
http://bigcouch.cloudant.com/api
Robert Paul et.al will help getting the
On Mar 31, 2013, at 21:48 , Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Sun, Mar 31, 2013 at 9:42 PM, Jan Lehnardt j...@apache.org wrote:
We will be collecting things here:
https://issues.apache.org/jira/browse/COUCHDB-1756
There is an (incomplete) list of differences down on:
It's not going away. It still exists on the back end interface, but it's the
admins job to purge at all replicas. The AP clustering model cannot guarantee a
cluster-wide purge.
The reason BigCouch doesn't support purge is that we need to synchronise
replicas of the same shard. Purging removes
That said, it would be great to reap state that we will never need again, it
just mustn't happen before every replica has seen it.
Sent from my iPhone
On 31 Mar 2013, at 20:55, Jan Lehnardt j...@apache.org wrote:
On Mar 31, 2013, at 21:48 , Dirkjan Ochtman dirk...@ochtman.nl wrote:
On
Dave, what tests do you have exactly failing?
I got nine (consistently) failing tests. However, it might be possible
that a few of them are timeout related, as I'm still working with
spinning discs (do you remember those?) on my computer here. That's why
I'd like to compare.
K
On Sun,
On Mar 31, 2013, at 22:43 , Klaus Trainer klaus_trai...@posteo.de wrote:
Dave, what tests do you have exactly failing?
I got nine (consistently) failing tests. However, it might be possible
that a few of them are timeout related, as I'm still working with
spinning discs (do you remember
On Sun, 2013-03-31 at 22:46 +0200, Jan Lehnardt wrote:
On Mar 31, 2013, at 22:43 , Klaus Trainer klaus_trai...@posteo.de wrote:
Dave, what tests do you have exactly failing?
I got nine (consistently) failing tests. However, it might be possible
that a few of them are timeout related,
32 matches
Mail list logo
