Am 2020-11-16 um 18:23 schrieb Oleg Kalnichevski:
On Mon, 2020-11-16 at 18:07 +0100, Michael Osipov wrote:
Am 2020-11-16 um 17:56 schrieb Oleg Kalnichevski:
On Sun, 2020-11-15 at 19:17 +0100, Michael Osipov wrote:
That was it. Gavin added the permission and it works now.
What's is next from your POV?


If at all possible could you please look into an automated way of
stitching together content of different artifacts / releases?
Presently
this is one of the biggest pain points for me as a release manager.

Can you tell what you do today? The easiest way which comes to my
mind
is apply the same way we do with Maven:

mvn -Preporting site site:stage
mvn scm-publish:publish-scm

When staging is not required:
mvn site
mvn site-deploy

the scm-publish-plugin will do the rest for you.

Do you want to automate on tagging too or is that sufficient?


I manually generate content from the main project website and one or
several product releases with `svn site`, stage the content locally,
manually fix broken links, manually fix inconsistent line endings,
manually commit to the SVN repository.

I have pushed site-deployment branch in core. Here is roughly the procedure to push the site for a release:

Consider you have completed "mvn release:prepare release:perform", now do:

$ cd target/checkout
$ mvn site site:stage
$ mvn scm-publish:publish-scm

The site has now be staged at https://svn.apache.org/repos/asf/httpcomponents/site/httpcomponents-core-archives/httpcomponents-core-LATEST/

Send the vote email and present the staged site. When the vote passes do the following:
$ svnmucc -m "Publish httpcomponents-core-5.0.x 5.0.4 documentation" \
  -U https://svn.apache.org/repos/asf/httpcomponents/site \
  cp HEAD httpcomponents-core-archives/httpcomponents-core-LATEST 
httpcomponents-core-archives/httpcomponents-core-5.0.4 \
  rm httpcomponents-core-5.0.x \
  cp HEAD httpcomponents-core-archives/httpcomponents-core-LATEST 
httpcomponents-core-5.0.x


The plugin will solve most of the issues mentioned, the broken links need to be discussed further. We also need to discuss the skin especially for the custom CSS.

We need to break up httpcomponents-website and push pages from subprojects into the subprojects to make it work properly.

All taken from: https://maven.apache.org/developers/website/deploy-component-reference-documentation.html

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to