Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to share release notes on website #5722

Open
juliasilge opened this issue Dec 12, 2024 · 3 comments
Open

How to share release notes on website #5722

juliasilge opened this issue Dec 12, 2024 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@juliasilge
Copy link
Contributor

juliasilge commented Dec 12, 2024

We've got a very initial downloads page on our website here: https://positron.posit.co/download

One next step we need to take is to make release notes available on our website. Take a look at some different ways we might approach this:

Side note: I am noticing the big "download" button in the navbar on the VS Code docs site and like that a lot.

@juliasilge juliasilge added the documentation Improvements or additions to documentation label Dec 12, 2024
@juliasilge juliasilge added this to the Release Candidate milestone Dec 12, 2024
@juliasilge juliasilge self-assigned this Dec 12, 2024
@juliasilge
Copy link
Contributor Author

We are planning for not-very-automated release notes because we prefer for these to be more like a blog post (in fact, we would use it as a starting point for actual blog posts) and less like a list of issue titles as bullets.

@atheriel
Copy link

atheriel commented Dec 14, 2024

Tom tipped me off to this. Our experience with the pro products indicates that a surprising number of internal and external folks do read release notes, and few of them would be well-served by the "list of issue titles as bullets" approach. I'd be very happy to see Positron have narrative and end-user-friendly release notes, though I know that is this much more work!

@timtmok
Copy link
Contributor

timtmok commented Feb 11, 2025

Keeping a separate markdown file for each release would be my preference. Each monthly release gets its own file (1.95, 1.96, etc.) and the version is used in the link to it.

Doing it this way makes it easy to display the release notes in Positron. All the code for displaying release notes currently checks VS Code's server that hosts the release notes. The infrastructure is there for the "Show Release Notes" action to display a markdown file. What needs to change is where it gets the markdown file and how it compares versions to decide if an update just occurred.

The release notes viewer is also quite capable of showing blog style content. Images are easy to embed and linking it relative to the markdown file is all that's required. Video is also supported if we need it (VS Code uses mp4 files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants