> On Apr 18, 2021, at 6:38 AM, sebb <seb...@gmail.com> wrote:
>
> On Sun, 18 Apr 2021 at 13:40, Gary Gregory <garydgreg...@gmail.com> wrote:
>>
>> Note that git also has its gitlink and sub modules features that we could
>> use here.
>
> Are they easy to use?
Submodules are documented at
https://git-scm.com/book/en/v2/Git-Tools-Submodules. It is a pretty short read.
In a sense it is a replacement for the .asf.yaml in the submodules. Every
sub-project would still likely have its own repo but you could get them all
just by cloning the parent repo with some extra flags on the clone. When you
commit changes to the sub-module they still go back to the individual repos,
not the parent.
> Who is going to design and test the replacement?
> Will such a design really be easier to use?
> There's no point changing the publication strategy if it is not an
> improvement.
Unfortunately, I can’t answer that. I don’t recall ever updating any of the
Commons web sites.
>
> We do at least have a way forward if Infra insist on removing
> websites/production.
> Simple to implement, but tedious, as nearly every proper component POM
> will need updating, and existing checkouts will need replacing.
> At least it's a one-off change, and it won't change processes, except
> perhaps for the top-level site.
Having gone through a similar process and after reviewing
http://commons.apache.org/site-publish.html I’d have to say that the effort
isn’t really much different. Logging Services hasn’t implemented any automation
around publishing to the main site as Commons seems to do, but it certainly
wouldn’t be hard to create a GitHub action to do it.
The main difference I see is that the current commons process seems to deploy
directly to the live site. With Git all your commits should go to the
ash-staging branch and the automation should be building that. Making it go
live is as simple as:
git checkout asf-site
git rebase asf-staging
git push
This allows you to validate the site before it goes live.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
