lofwyr14 commented on PR #113: URL: https://github.com/apache/myfaces-homepage/pull/113#issuecomment-3605555880
It is good to correct spelling mistakes. However, this must be done at the source. Subsequent changes to releases are to be discarded. In general, this is my point of view: **Releases must be immutable** Under ASF policy, a published release artefact (including Javadoc and XSDs) must not be changed; any modification, even spelling fixes, effectively creates a new release that hasn’t gone through the formal process. **Reproducibility and trust** Users must be able to verify that what they have matches the signed release. If we silently edit generated docs, the content no longer matches the original source + build at release time. **Auditability and legal provenance** ASF emphasizes clear, traceable provenance of what was released and when. Post-hoc edits blur that boundary and can complicate legal or compliance questions later. **Version history clarity** The documentation associated with version X.Y should represent exactly what was shipped as X.Y. If we want corrected docs, they should be published as part of a new release or as separate, clearly marked, website content (e.g. “fixed docs” or errata), not by rewriting the original artefacts. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
