Update announcement text from Param 2.4 to Param 2.4.1#1164
Update announcement text from Param 2.4 to Param 2.4.1#1164Coderambling wants to merge 1 commit into
Conversation
|
To me, it doesn't seem necessary to announce point releases. |
Thanks @jbednar . To me it seems more informative to announce them, but made this PR because I was assuming there was a guideline / policy. Should there be one (that states only announce .x releases, not x.y releases)? |
|
That's a topic that could be discussed on the Discord server. If there is a consensus, happy to have it apply to this project and to other HoloViz repos. |
|
-1 on this. My original intention with the banner was to point users to the blog post so that they can find out about new features, breaking changes, and all. Patch releases don't deserve that kind of attention. |
That is also what I see as one of the functions of the banner. But it also functions to announce to / alert recurring visitors to the site that there has been a new release. For that group, who presumably include devs that are active users, that seems pretty relevant info. Especially as the changes seem to be non-trivial, in the sense that they solve some bugs / real frustrations for devs. Or am I overestimating the impact of the release? Opened a Discord thread for discussion. https://discord.com/channels/1075331058024861767/1524738910687723630 To be clear: proposed the change under the assumption that the version number in the website banner was intended to show the very atest x.y.z release. #1153 might have (erroneously) played into that assumption. 🚀 Features |
3 participants
Or is the policy for Param to not announce point releases in the announcement banner on the parameter website?
For comparison, the release text on the Panel website does state the point version.