Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Message-ID: <555D4635.8020104@gmail.com>
Date: Wed, 20 May 2015 22:43:01 -0400
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: dev@accumulo.apache.org
Subject: Re: Ease of making release candidates (was: Javadocs in binary
 "release")
References: <555CBD0F.9000907@gmail.com>
 <CAL5zq9beK0p6KC+rjy74UgznOa_j1Ts7tHy1TMgTu7kMYny7Hw@mail.gmail.com>
 <555CD535.80007@gmail.com>
 <CAL5zq9bRz29nUv1qHLj_Q2EkKmK+_LfCjcTqODkMC9k9rhZFYQ@mail.gmail.com>
 <555D1B1D.9020904@gmail.com>
 <CAL5zq9ZzbkgQbTUorGMMy6f_eiAvh3JWGii+2EjpMGK71Eza3A@mail.gmail.com>
In-Reply-To: 
 <CAL5zq9ZzbkgQbTUorGMMy6f_eiAvh3JWGii+2EjpMGK71Eza3A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Christopher wrote:
> On Wed, May 20, 2015 at 7:39 PM, Josh Elser<josh.elser@gmail.com>  wrote:
>> Christopher wrote:
>>>> The other half of me wanting to fork off this convo is that there's also
>>>>>   more to making a release than just making the release candidate. I
>>>>> probably
>>>>>   had 30+ commits to CMS over the past week (granted some of which were
>>>>> me
>>>>>   just editing content on CMS), but we have a lot of steps which are now
>>>>> just
>>>>>   copying files from the release, committing to the site repo. I'd love
>>>>> to see
>>>>>   more done for automation here that can reduce the pain for the post-RC
>>>>> work.
>>> [snip]
>>>
>>> +0.5 to that. I'm willing to help a bit here, but it's a bit daunting,
>>> and it's not even clear to me where we can automate, especially with
>>> CMS being involved as a middle-man.
>>>
>> Yeah, I have _no idea_ what this kind of automation would look like. Trying
>> to keep it somewhat decoupled from CMS itself would be good (as it may go
>> away in the future -- or at least look different). It was just a pain point
>> that I noticed. I went back and forth picking files from the source release,
>> putting them in CMS, verifying they rendered right, etc.
>
> One thing you could have done is update all the files before clicking
> "commit". CMS is basically a web interface for a local SVN checkout.
> You can update many files in this local SVN checkout, examining each
> preview render, before ultimately clicking "Commit" which initiates a
> final rendering to the staging site. You definitely don't have to
> commit one file at a time.

The piecemeal operation wasn't due to working with CMS, but the fact 
that I repeatedly went back and forth saying "ok, I need to copy this", 
*looks to see what to do next*, "ok, now copy this", etc.

I have often used SVN directly to update the site.