Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of mainerror@gmail.com designates
 209.85.212.172 as permitted sender)
MIME-Version: 1.0
Sender: mainerror@gmail.com
In-Reply-To: <FEF61679-798E-4052-B359-263D433E1C63@apache.org>
References: <etPan.524333c4.6b8b4567.3d7e@akai.jsonified.com>
	<CAKmKYaC=9yydJCThvPmJdqDcrKsPCBXAC85YhBRB9k=YpWTQUQ@mail.gmail.com>
	<etPan.524359cf.238e1f29.3d7e@akai.jsonified.com>
	<FEF61679-798E-4052-B359-263D433E1C63@apache.org>
Date: Thu, 26 Sep 2013 11:03:08 +0200
Message-ID: 
 <CAGt9U8j7B8_sw=QA3yJwKOVMZrfg=jppyokWfoe5aTC42Mzauw@mail.gmail.com>
Subject: Re: [DISCUSS] push minor doc improvements/additions directly to
 release branches
From: Octavian Damiean <odamiean@linux.com>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001a11c33fd078f69404e745a368

--001a11c33fd078f69404e745a368
Content-Type: text/plain; charset=UTF-8

+1. Docs with minor issues trumps bad docs.


On Thu, Sep 26, 2013 at 10:57 AM, Garren Smith <garren@apache.org> wrote:

> +1 I agree, SHIP ALL THE DOCS!!!!
>
>
> On 25 Sep 2013, at 11:46 PM, Dave Cottlehuber <dch@jsonified.com> wrote:
>
> >> On Wed, Sep 25, 2013 at 9:04 PM, Dave Cottlehuber wrote:
> >>> Would there be any objections to pushing minor doc fixes & additions
> directly to master?
> >>
> >> No! In fact, I was doing that already even before 1.3.1 came out, I
> think.
> >>
> >>> The quicker we can get updates out into docs.couchdb.org, the better.
> >>>
> >>> To be clear, I'm not suggesting that major changes like Alex's branch
> should just go straight in.
> >>
> >> We talked about this in IRC today, but I'll reiterate here for those
> >> who missed that: I think Alex's work on the docs branch is awesome,
> >> but I feel like the branch has dragged on for way too long. This means
> >> uncounted users have gotten worse documentation than they could have
> >> gotten, because we were still tweaking some little thing or not quite
> >> satisfied with the language somewhere. While this kind of thing can be
> >> unavoidable with code, where there's much more complexity to deal
> >> with, documentation isn't like that, and we shouldn't treat it like
> >> that. Documentation patches should go straight to master or on very
> >> short-lived feature branches.
> >>
> >> Cheers,
> >>
> >> Dirkjan
> >>
> >
> > +1 to that. Dirkjan's right, and it's past time for the superb work Alex
> has put in to make the light of day :-)
> >
> > SHIP ALL THE DOCS!
> >
> >
>
>


-- 
Octavian Damiean

GitHub: https://github.com/mainerror

--001a11c33fd078f69404e745a368--