Just a heads up what options we will have with the new website and a preview on a possible new release distribution system.
Currently our website and documentation are in our confluence wiki and being automatically exported to HTML and subsequently being rsync'ed to the ASF's webservers. In the future, the rsync step will cease to exist. Instead a buildbot job will run a special maven plugin hourly that exports the website to HTML and checks it into a repository at [1] from where it will be picked up from the ASF webservers almost instantly. This also means that we can commit to this repository and changes will be live almost instantly, e.g. for per-release content, such as JavaDocs. We just have to commit them during our release process. Another thing that we might want to consider is switching our release process to the new dist system being offered by the ASF [2]. It basically allows us to commit release candidates to [3] and upon a successful vote svn mv them to [4] from where they will be picked up immediately by the mirror system. No more SSH uploads and waiting involved. Should we pursue this? Uli [1] https://svn.apache.org/repos/infra/websites/production/ [2] http://www.apache.org/dev/release#upload-ci [3] https://dist.apache.org/repos/dist/dev/ [4] https://dist.apache.org/repos/dist/release/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
