Le lundi 16 novembre 2020, 18:40:48 CET Michael Osipov a écrit :
> 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.
> 
> Alright, I will set up a branch for core5 first and will let you play
> first with it.
notice: on manually fixing inconsistent line endings and commiting to svn, this 
will be done by scm-publish plugin
on fixing broken links, this is where some tests will be required

and there will probably be a question on moving handwritten content from main 
website (in subdirectories of [1]) to your components documentation

let's work on that branch

Regards,

Hervé

[1] https://github.com/apache/httpcomponents-website/tree/master/src/site/apt

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





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

Reply via email to