On a second though, the downside with this approach is that the change
log will not be visible during a vote. Not sure if this is a blocker or
if directing voters to read the change log on Github is okay.
On 20/04/2022 10:00 pm, Francis Chuang wrote:
I noticed that some changes to Calcite's changelog was deployed to the
website automatically: https://calcite.apache.org/docs/history.html
The reason is that in the Github Actions workflow
(https://github.com/apache/calcite/blob/master/.github/workflows/publish-non-release-website-updates.yml#L24),
we deploy the site immediately when we update the history.md file. This
is because after a release, there's a possibility that we might need to
go back to update the release date or to make some small tweaks to the
changelog.
I was wondering if we can change history.md, so that the changelog for a
release is only visible if there's a release announcement in the _posts
folder, similar to how the downloads page is generated.
Would anyone familiar with jekyll like to take a stab at this?
