I am pretty confident in my changes, so I will commit them directly to trunk,
then Rob (or whoever wants to) can glance over them in staging and see that
they meet expectations, or whether more is needed.
Now, on to recreating work. {grumble, grumble}
> You may find them still in your copy of the site in CMS.
That's what appears to be gone!
---
A. Soroka
The University of Virginia Library
> On Nov 8, 2016, at 9:38 AM, Andy Seaborne <a...@apache.org> wrote:
>
>
>
> On 08/11/16 14:31, A. Soroka wrote:
>> Well, this is pretty infuriating. I did not 'extra-commit' the changes I
>> made to the HTTP auth docs, apparently, or something of the sort, and they
>> are all now gone. So I will have to redo those.
>
> Very annoying.
>
> You may find them still in your copy of the site in CMS.
>
>> I have read the documentation repeatedly and I do not understand the
>> web-based CMS interface at all. I will be using SVN directly from now on.
>
> Same here.
>
>> I will do that work immediately and commit it directly. Andy et al, do you
>> think this is worth republishing the site? Right now, we are hanging out
>> there a bit with HttpAuthenticator and subtypes gone and no docs as to what
>> to do, exactly the situation Rob Vesse wanted to avoid.
>
> For me, republishing is fine - it's not necessary to sync it with a release
> (it does not need a vote). We have tended to sync because changes build up
> about the next release and so some care is needed about any "ahead of time"
> documentation that is on staging.
>
> It is svn - if necessary we can branch etc. It is simpler to not go so until
> needed. Only trunk can be published IIRC.
>
> Andy
