nchammas commented on PR #699: URL: https://github.com/apache/spark-website/pull/699#issuecomment-5086349643
> To be clear this is an explicit but temporary veto on changing the website build until after 4.2.0/4.1.3/4.0.4/3.5.9 are all released. It looks like [these releases are all complete][1]. @holdenk - Am I OK to mark this PR as ready for review? [1]: https://spark.apache.org/news/index.html To summarize the next steps given what we've discussed so far: 1. Review and merge this PR. It will eliminate the need for anyone to generate or commit HTML in their PRs. 2. The committer who merges this PR in should check the site immediately after the build runs to confirm the site deployed correctly and no revert is needed. (I believe that what broke the site in #697 was not related to the generated HTML, but I cannot be sure since we don't have a staging site!) 3. In the future, we should explore the following further improvements to the website workflow, both of which are valuable: - Setup a dedicated staging site where we can test sensitive changes. If possible, setup automatic staging sites that spin up for each PR. - Split the Markdown source and HTML output into separate branches. Does this sound good to everyone? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
