On Thu, 8 Dec 2022 at 10:17, Gilles Sadowski <gillese...@gmail.com> wrote: > > Le jeu. 8 déc. 2022 à 00:32, sebb <seb...@gmail.com> a écrit : > > > > On Wed, 7 Dec 2022 at 13:20, Alex Herbert <alex.d.herb...@gmail.com> wrote: > > > > > > So I can see the file to edit is index.html at this location: > > > > > > svn checkout --depth files > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > But should this be edited manually, or is it generated/updated via > > > some automation? > > > > That URL is where the website is served; when the site is built from > > source it will be overwritten. > > > > The actual site source is here: > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > There is some documentation here: > > > > https://commons.apache.org/site-publish.html > > > > > I ask as the newly released statistics component entry requires more > > > than just a version number to be updated. The entire link and badge > > > requires adding. > > > > That needs to be done here I think: > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/xdoc/index.xml.vm > > Thanks for the reminder. > > Main web site has been updated.
I have corrected the doap files to match those in conf/component_releases.properties so that running this: > conf/parse-latest-release.py currently makes no changes. This mainly added releases that have been manually updated in the component_releases.properties but not in the doap file. Only the latest Jexl 3.2.1 release required an update and the release date for compress 1.22. The following link is still out-of-date on the main site: jexl 3.2 -> 3.2.1 When I build locally (see below) there is no svn diff and the link is correct in the staging area at: https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html Gilles, it looks like (from the commit message) that you ran commons-site-publish.sh. But somehow the link for Jexl is still pointing at 3.2 and not 3.2.1. So I do not know what went wrong for this link. For the release process: After the component doap file is updated then the commons site should be rebuilt. This used to be done by a build-bot but now must be done manually. This requires running: > svn co https://svn.apache.org/repos/asf/commons/cms-site/trunk/ ==> edit doap/doap_<component>.rdf > conf/parse-latest-release.py > svn diff => check you have not downgraded other components - fix their doap file and repeat > svn commit conf doap -m 'Regenerated component releases' > commons-site-build.sh > svn diff target/site > svn commit target/site -m 'Update the staging site prior to deployment' => inspect at https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html > commons-site-publish.sh => inspect target/commons-site-publish.svnmucc => Run svnmucc command printed by the script If this is correct then I can update the release guide we use in the math-derived component to reflect these steps. Alex Alex --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
