On 03/21/2013 04:17 PM, Noah Slater wrote:
Yes, there should be an item in CHANGES. (On all branches.)
Ok, I'll add this to CHANGES for both right now.
Also, does this need to be applied to more than just 1.2.x, 1.3.x, and
master?
I've not seen this behavior in 1.0.x, I have in 1.1.x however. This is a
harmless patch for both 1.0.x and 1.1.x. Thoughts?
See list of current releases:
http://wiki.apache.org/couchdb/CurrentReleases
On 21 March 2013 23:11, Wendall Cada <[email protected]> wrote:
Patch has been applied to 1.2.x. Everything is good from my perspective. I
could add something to CHANGES about this, but I'm not certain it's worthy
of noting. Let me know if this is necessary, I'll be glad to add comments.
Wendall
On 03/21/2013 11:26 AM, Noah Slater wrote:
When you say "added", do you mean the patch should be applied to the 1.2.x
branch?
On 21 March 2013 18:21, Wendall Cada <[email protected]> wrote:
https://issues.apache.org/****jira/browse/COUCHDB-1449<https://issues.apache.org/**jira/browse/COUCHDB-1449>
<https**://issues.apache.org/jira/**browse/COUCHDB-1449<https://issues.apache.org/jira/browse/COUCHDB-1449>>should
be added to 1.2.2, this was a blocker for 1.3.0, but somehow was
missed.
Wendall
On 03/21/2013 08:51 AM, Noah Slater wrote:
Dear community,
I would like to propose that we prepare Apache CouchDB 1.2.2-rc.1.
The project aims to produce time-based releases. If your favourite
feature
is not ready for this version, it can be included in the next version.
However, if you know of anything that should block the release, please
speak up now.
The 1.2.2 NEWS entry as it stands:
* Fixed rewrite counter bug.
The 1.2.2 CHANGES entry as it stands:
https://git-wip-us.apache.org/****repos/asf?p=couchdb.git;a=**<https://git-wip-us.apache.org/**repos/asf?p=couchdb.git;a=**>
blob_plain;&f=CHANGES;hb=1.2.**x<https://git-wip-us.apache.**
org/repos/asf?p=couchdb.git;a=**blob_plain;&f=CHANGES;hb=1.2.x<https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob_plain;&f=CHANGES;hb=1.2.x>
**>
Are these accurate? Please double check any work you may have done and
make
sure that the corresponding NEWS and CHANGES entries are up-to-date.
Thanks,
