CouchDB 1.2 was released in April, we've certainly not rushed 1.3. :) Releasing on a regular basis seems sensible, and the group doing the work came to that conclusion together, it doesn't oblige you to upgrade to a release that doesn't contain features or fixes you need.
B. On 14 November 2012 00:07, john.tiger <[email protected]> wrote: > this feels rushed - not a good thing with an enterprise thing like a db - > does couch have big users that need the as is 1.3 features asap or even > sponsors that are wanting to ship every 3 mos regardless ? If not, why not > wait and rally troops to make sure cors features are set, documentation is > done, and some compiling issues are resolved - maybe the committee has > other reasons, but 3 mos seems really quick for an enterprise thing like a > db. > > Others mlge may vary but we want to use the cors feature - could care less > about a 1.3 without it > > > > > On 11/13/2012 01:08 PM, Jan Lehnardt wrote: > >> On Nov 13, 2012, at 20:53 , Benoit Chesneau <[email protected]> wrote: >> >> On Tue, Nov 13, 2012 at 8:51 PM, Jan Lehnardt <[email protected]> wrote: >>> >>> if it's part of 1.3. >>>>> >>>> The point of this email is to decouple cors & docs from 1.3.0. >>>> >>>> >>>> I forgot a "not" obviously.. Sorry for that >>> >> Clarified via IRC: >> >> [21:00:26] <benoitc> well was just me trying to ask "do we really want to >> ship at least without docs? " >> [21:00:39] <benoitc> but i'm fine with both >> [21:00:40] <+jan____> ah, I’d say yes. >> [21:01:12] <benoitc> i wonder if we couldn't put the doc online for 1.3 >> at least >> [21:01:39] <benoitc> since that part can be easily done >> http://rcouch.org/docs/ >> [21:01:58] <+jan____> sure, why not, that’s completely unrelated to the >> release >> [21:02:18] <benoitc> indeed >> >> Cheers >> Jan >> > >
