You just commit the changed files to the svn repo where the site is located. I forget which repo it is, but there was a notification email recently from when Ralph committed the site a couple days ago.
On 1 September 2017 at 04:32, Mikael Ståldal <mi...@apache.org> wrote: > Yes, that part I know. But how do I then publish the web site? > > > > On 2017-08-31 22:17, Ralph Goers wrote: > >> That is actually documented in the original release vote email. >> >> a) for a new copy do "git clone https://git-wip-us.apache.org/ >> repos/asf/logging-log4j2.git <https://git-wip-us.apache.org >> /repos/asf/logging-log4j2.git> <https://git-wip-us.apache.org >> /repos/asf/logging-log4j2.git <https://git-wip-us.apache.org >> /repos/asf/logging-log4j2.git>>" and then "git checkout >> tags/log4j-2.9-rc1” >> b) for an existing working copy to “git pull” and then “git checkout >> tags/log4j-2.9-rc1” >> >> >> On Aug 31, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote: >>> >>> How can I do that? >>> >>> On 2017-08-28 18:18, Ralph Goers wrote: >>> >>>> Oh, and if you check out from the release tag and create a branch the >>>> web site fixes can be made there after the release is complete. >>>> >>> >>> >>> >> >> > -- Matt Sicker <boa...@gmail.com>
