search

microsoft / msix-packaging

MSIX SDK
MIT License
987 stars 166 forks source link

[BUG] Use clearer unique git tag info for MSIX Core preview releases #446

Open jfkw opened 3 years ago

jfkw commented 3 years ago

Project MSIX SDK

Describe the bug I receive email notifications for MSIX Core preview releases with differing changelog information, yet all release notices refer to identical git tag info: microsoft/msix-packaging - Tag: MSIX-Core-preview - Commit: 16737c0 , and a non-incrementing artifact number msixmgrSetup-1.1.56.0-x64.msi. It would help users and packagers if a unique git commit id and incrementing version number accompanied each release notification or instructions were provided on how to find that information in git history and tags.

To Reproduce Subscribe to github notifications for releases and receive emails.

Expected behavior Emails announcing new releases should include a unique git commit id identifying that particular release. For users or packagers tracking the preview releases, including a unique git content hash and/or tag identifier is essential for packaging automation tools to work.

Screenshots Emails containing microsoft/msix-packaging - Tag: MSIX-Core-preview - Commit: 16737c0 , and non-incrementing artifact number msixmgrSetup-1.1.56.0-x64.msi.

Platform

Additional context I would like to make RPM packaging for msix-packaging. Even in the prerelease phase, using incrementing version numbers or at a minimum unique git content identifier for all releases would be very helpful for this purpose. I would also like to know the "base version" that this prerelease is expected to use when it reaches general release. Is it 1.1.56.0?

jfkw commented 3 years ago

Thank you again for the regular releases of MSIX Core preview. Can you also please add a regular git annotated tag upon each release? i don't see any other way to reference this information in git history. A packager is obliged to look at the generated Changelog items and manually find the newest included commit. The following works well in my local git clone:

git tag -a 'v1.1.58.0' -m 'v1.1.58.0'

Any other spelling indicating "preview" status would work equally well. This addition of git tags to the preview release workflow would be a tremendous help to those who would like to package the SDK.