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? 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. Alex On Tue, 6 Dec 2022 at 23:58, Gilles Sadowski <gillese...@gmail.com> wrote: > > Le mer. 7 déc. 2022 à 00:31, sebb <seb...@gmail.com> a écrit : > > > > On Tue, 6 Dec 2022 at 22:28, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > > > Hello. > > > > > > Homepage > > > https://commons.apache.org/ > > > contains inconsistent information: Some "(maven-central) badges" display > > > a version number but the link points to another (usually older) one. See > > > e.g. > > > * RNG > > > * Geometry > > > * Imaging > > > * Numbers > > > * Compress > > > * Pool > > > * JCS > > > * Math > > > * Configuration > > > * Text > > > * Net > > > * ... > > > > That's because the version data has not been updated in the relevant > > status file. > > RMs should ensure that the file is updated upon release. > > > > The badges are generated dynamically from Maven Central metadata, so > > are whatever the image.shields.io website thinks is the latest. > > > > IMO these invisible dynamic queries go against the Privacy FAQ: > > > > https://privacy.apache.org/faq/committers.html > > > > I think it would be better to have a regular batch job to ensure the > > status file is up to date and not rely on a 3rd party. > > > > Sorry, I'm fairly lost here; I don't know what "image.shields.io" is. > Nor when/how we started having those links/badges generated. > > I seem to remember that the RM had to update this file: > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/conf/component_releases.properties > and the appropriate file in > https://svn.apache.org/repos/asf/commons/cms-site/trunk/doap/ > > But then? Is there a script to run so that the site is updated? > > > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
