Can we have a changelog?
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@MaximRouiller Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
@MaximRouiller - The storage engineering team has said that there are no changes beyond just upping service version numbers accepted. Also note that this does not mean the service version's functionality was implemented.
The team is actively directing customers to the new Azurite emulator. Our docs will be updated to reflect this in the near future.
@mhopkins-msft - FYI
As long as Visual Studio ships with Azure Storage Emulator by default (and not Azurite) I think release notes still matter for the time being?
@kpstolk - It's not that they don't matter, but we won't be further augmenting the release notes that are currently found at https://docs.microsoft.com/azure/storage/common/storage-use-emulator#storage-emulator-release-notes, because Azurite will be the recommended emulator going forward.
Isn't it normal to have release notes for software that we release?
If they are not found in our docs? Where can they be found? I'd be fine if it was on GitHub but this project isn't open source and we can't inspect what changed between the different versions.
On my side, I ended up with breaking changes between two versions. What changed? 🤷♂
Release notes are necessary.
The only release notes we have for the soon-to-be-legacy emulator are here:
https://docs.microsoft.com/azure/storage/common/storage-use-emulator#storage-emulator-release-notes
The engineering team has said that nothing has changed from v5.7 to present except the update to the new service version. If you found up with a breaking change between versions, then please contact support, as there is nothing more for us to document here.
@tamram Currently debugging a Functions project from Visual Studio automatically starts the Azure Storage Emulator.
Will this be replaced with Azurite since you say the Azure Storage Emulator will be legacy soon?
I see that I can also install a NuGet package which launches automatically instead but the latest version is more than a year old and links to an archived GitHub repo..
We should consider reopening this and giving at least something in the changelogs.
Did they fix bugs? Did they fix a regression? Was there performance improvements?
No information means to a reader that the doc is outdated.
Just my 2 cents.
+1 to @MaximRouiller. We should absolutely be shipping changelogs even if they're absolutely trivial changes for something that is soon-to-be legacy.
Since it was mentioned that the only change from 5.7 to 5.8 and 5.8 to 5.9 is a simple dependency (service version) update, the additional entries should be relatively simple ❤️
I'd suggest something along the lines of the following, and would be happy to PR them via whatever processes are necessary to land them if I can get the details in angle brackets:
## Version 5.9
The storage emulator now supports version <version identifier> of the storage services on <Azure product> services endpoints.
## Version 5.8
The storage emulator now supports version <version identifier> of the storage services on <Azure product> services endpoints.
You can see that there's prior art for this approach on Version 5.6, Version 5.3, Version 4.3, and others.
Most helpful comment
We should consider reopening this and giving at least something in the changelogs.
Did they fix bugs? Did they fix a regression? Was there performance improvements?
No information means to a reader that the doc is outdated.
Just my 2 cents.