+1 Commented release notes seem to be an easy solution. -- Michael Mior mm...@apache.org
Le mer. 20 avr. 2022 à 10:00, Julian Hyde <jhyde.apa...@gmail.com> a écrit : > Usually we don’t add release notes to history.md until the RC vote, so > this isn’t a problem. > > But occasionally we want to start writing the rekease notes early. An > example is my recent change to upgrade Avatica’s gradle and Java. For such > changes we could add the release notes for the upcoming release commented > out, and the release manager could uncommon them when preparing the RC. > > What you think? > > Julian > > > On Apr 20, 2022, at 5:33 AM, Michael Mior <mm...@apache.org> wrote: > > > > I don't necessarily see this as a problem, although instead of > 2022-MM-DD > > for the release date, it might be nice to clearly indicate this is > > unreleased. > > -- > > Michael Mior > > mm...@apache.org > > > > > >> Le mer. 20 avr. 2022 à 08:00, Francis Chuang <francischu...@apache.org> > a > >> écrit : > >> > >> 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? > >> >
