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

SNOW-1902938: Missing release notes for version 4.3.0 #1092

Closed
julealgon opened this issue Jan 29, 2025 · 4 comments
Closed

SNOW-1902938: Missing release notes for version 4.3.0 #1092

julealgon opened this issue Jan 29, 2025 · 4 comments
Assignees
Labels
question Issue is a usage/other question rather than a bug status-triage_done Initial triage done, will be further handled by the driver team

Comments

@julealgon
Copy link

Version 4.3.0 was just published:

It links to this page for release notes:

But the page only lists 4.2.0 as the latest release.

Can you please update the documentation page with information regarding version 4.3.0?

@github-actions github-actions bot changed the title Missing release notes for version 4.3.0 SNOW-1902938: Missing release notes for version 4.3.0 Jan 29, 2025
@sfc-gh-dszmolka sfc-gh-dszmolka self-assigned this Jan 30, 2025
@sfc-gh-dszmolka sfc-gh-dszmolka added question Issue is a usage/other question rather than a bug status-triage_done Initial triage done, will be further handled by the driver team labels Jan 30, 2025
@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Jan 30, 2025

fair point. but please be aware that Snowflake's documentation, strangely, has absolutely nothing to do with this library in a sense that they are two separate codebases, approval flows, and the rest. So if you can allow us some leniency after a release, like couple of days, that would be appreciated :)
if you need literally immediate access to what changed after a release, I can recommend comparing the current tag with the previous. In this particular case, comparing 4.3.0 with 4.2.0.

Updating the documentation is in progress and after approvals, it will be visible. Thank you for bearing with us while it is deployed !

@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Jan 30, 2025

I see that now (30 Jan 2025 07:59 UTC, ~ 11 hours after you submitted this issue) https://docs.snowflake.com/en/release-notes/clients-drivers/dotnet-2025 already has 4.3.0, so a little patience helps ;)

@julealgon
Copy link
Author

fair point. but please be aware that Snowflake's documentation, strangely, has absolutely nothing to do with this library in a sense that they are two separate codebases, approval flows, and the rest. So if you can allow us some leniency after a release, like couple of days, that would be appreciated :) if you need literally immediate access to what changed after a release, I can recommend comparing the current tag with the previous. In this particular case, comparing 4.3.0 with 4.2.0.

Updating the documentation is in progress and after approvals, it will be visible. Thank you for bearing with us while it is deployed !

I understand what you are saying, but keep in mind that keeping track of the docs after the release notification on github has already fired adds overhead to consumers. I usually subscribe to github releases of libraries we use, and I keep close tabs on those notifications to see what the new library versions provide. I will usually get to those notifications with at most a few hours of delay as I check github multiple times during work.

If I may provide a suggestion to improve this a bit without changing your workflow, it would be very nice if you could at least provide a specific link to the release notes for that version, instead of linking to a generic hub page. That way, I could for example just open a separate tab and watch when the page becomes available.

I assume you know upfront what the URL of a given new release will be, such as this new one:

so a little patience helps ;)

Do not assume I created this issue due to "lack of patience", because that is definitely not the case. There was no way for me to know whether or not you just forgot the notes. I've started tracking this particular repository just recently.

@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Jan 30, 2025

We used to have the release notes in the same repo where the given library is, similarly to how snowflake-connector-python has it today. It was fantastic, realtime and easy to manage.

Requirements were different and now we have what you see today. Apologies for the difficulties. edit: Your feedback has been relayed to the relevant team, wanted to add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issue is a usage/other question rather than a bug status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

2 participants