Get final merges in to Ubuntu Docs

[Kevin Godby]

On Thu, Sep 12, 2013 at 9:08 PM, Doug Smythies <dsmythies at telus.net> wrote:
> On 2013.09.12 17:17 Benjamin wrote:
>> Oh and although we can all push directly its still best to merge propose
>> and have all pushes peer reviewed. This is what all teams do and it helps
>> prevent problems with changes.
>
> My opinions only (feel free to disagree):
>
> It depends on: How trivial the change is; How responsive other doc
> committers
> are; How much time is available (it takes a lot of extra time to go the
> merge
> proposal route); If there are actually others helping and contributing.
>
> In an ideal world, one with lots of contributing volunteers, I agree with
> you.
> However, I have become fed up waiting around for merge proposals to be
> approved.
> For example take a look at the one I have sitting over on the serverguide
> right
> now. Enough already, I'm going to push it myself.

I concur with Doug on this issue.  At this point in the release cycle,
we're short on time. Adding the merge-proposal roadblock will just
serve to slow things down.

I think that once the documentation is up to date and we have
reconstituted the ubuntu-docs team, using merge proposals is a good
idea. It's always good to have another set of eyes on changes before
they're merged into the main branch.

Right now, though, we're short on manpower and short on time—both
necessary for managing merge proposals. So for the remainder of the
13.10 cycle, I think we should continue pushing ahead and trying to
get as much done as possible as quickly as possible.

—Kevin