Hi Nuno,
thanks for offering your help!
I don't think we wait for something from you, we are just trying to
somehow get the repo transferred to the ASF so we can retain the
issues. One thing we have to get working on the ASF side for it is to
enable GitHub issues for the repo which are disabled b
Proedurally, CouchDB 2.0 is effectively in feature freeze - we need to
get it out the door, it is far overdue.
Looking at changing basic functionality like _rewrite can come after
2.0 is done, in the 3.0 timeframe.
-Joan
- Original Message -
> From: "Johs. E"
> To: "dev@couchdb.apache.o
Guys, to make sure are you waiting on any action on my behalf?
Happy to do whatever apache seems fit, a single official email from apache and
I’ll get it done,
Take care,
Nuno
—
Sent from Mailbox
On Fri, Sep 4, 2015 at 1:26 AM, Robert Kowalski wrote:
> Somehow I got no answer on the
Fellow CouchDB enthusiasts,
Let me quote a dialogue I had the other day with a colleague on Couchapps and
_rewrite:
> > I would like to know what is so horrible with the vhost/rewrite of CouchDB
> You must concentrate all rules in one place, that is totally out of idea ‘one
> app – one ddoc’
>
