On 08/03/2020 09:40, Roy Lenferink wrote:
Hi Andy,
Good to be pro-active on this! However, I had yet to send reply to this list
that the actual move was
already done :) See [1] for the actual change.
:-)
To verify: on jena.a.o the 'Edit this page' button is visible (meaning the site
is served from Git), and
this correctly redirects the user to the jena-site repository on GitHub.
Yes - "edit" is there.
https://jena.apache.org/documentation/javadoc/ was 404.
Fixed by change the layout but (for future reference), is it possible to
have content in :master:/documentation/javadoc/_index.md and then not
have it lost when branch javadoc is gitpubsub'ed. i.e does the
additional javadoc branch simply copy in more HTML pages or replace the
directory?
If it is copy-in, I'll change the change to preserve bookmarks.
Is polling scm (build job) something we want to set-up or are starting with
manually triggering the
build-job after changes are made?
Personally, I'd prefer to change to polling SCM.
We have typically published the site with the release, having used
"staging" to view changes. trunk had the role of "proposed".
If everyone is happy and setup for Hugo, we can change to master being
the ready-to-go real thing.
Andy
[1] https://github.com/apache/infrastructure-puppet/pull/1734
On 2020/03/08 08:55:37, Andy Seaborne <[email protected]> wrote:
Request made to move from svn+CMS to gitpubsub:
https://issues.apache.org/jira/browse/INFRA-19939
Andy
