Committing the site to SVN certainly takes a lot longer than committing it to Git when publishing the staging version. Perhaps we can try out GitPubSub for the CMS functionality instead of the traditional SvnPubSub?
On 22 January 2018 at 16:49, Ralph Goers <[email protected]> wrote: > https://wiki.apache.org/logging/Log4j2ReleaseGuide < > https://wiki.apache.org/logging/Log4j2ReleaseGuide> is fairly close to > being up to date. I try to update it whenever I change the process. Some of > the steps are one time only - like getting the signing key or setting up > Maven. > > I should add one more step before running the release build. I always > build the web site first and inspect it for problems before I start the > release. > > Basically, by the time I start running the release plugin I am pretty > confident I am going to vote +1 as all the tests have passed for me, I know > Maven is going to sign almost everything, and I have performed all the RAT > checks. Usually, getting to that point takes me several hours as I almost > always find new modules that are missing the license or run into a test > that fails and I have to create a new logo. Believe it or not, the second > longest part of the process is uploading the web site with each release. > The web site is pretty big. > > Ralph > > > > > On Jan 22, 2018, at 3:34 PM, Gary Gregory <[email protected]> > wrote: > > > > Hi All but mostly Ralph: > > > > Are all the instructions to release all of Log4j up to date on the wiki > > https://wiki.apache.org/logging ? > > > > Gary > > -- Matt Sicker <[email protected]>
