rlenferink commented on PR #99: URL: https://github.com/apache/comdev-site/pull/99#issuecomment-1490626581
> I've raised INFRA-24405 To be honest: I don't like the idea of globally installed tooling. Different projects are using different versions of Hugo (Celix uses 0.63.2, Jena uses 0.66.0, MINA 0.63.2, Directory uses Hugo, SIS, Nutch etc). What happens if we rely on version 0.111.3 and in quite some time another project asks INFRA to update to 1.0.0 (or another version which contains a breaking change). IMO users (different projects) should install what they need themselves (either in a container or in a temporary path as we previously did in the Jenkinsfile). Our website isn't gonna fix itself if INFRA decides to update Hugo within period X. It is better to be in full control then instead of e.g. a build starting to fail (or worse: some side effect we don't directly see, e.g. a successful build but the build generating broken URLs). (speaking from personal experience at `$work` that not pinning tooling versions is a path you don't want to take) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
