Summary
Create a shared technical baseline for Windows distribution so Microsoft Store and winget do not each invent their own package metadata, naming, and release conventions.
Motivation
Both distribution channels overlap heavily in the required metadata and packaging quality, for example:
- package/app name
- publisher name
- package identifier strategy
- versioning
- installer/package URL stability
- license/support URLs
- MSIX quality and install/upgrade behavior
This shared baseline should be defined once and then referenced by the channel-specific tickets.
Scope
Shared metadata
Define and document the canonical values for at least:
- Product name shown to users
- Publisher / vendor name
- Package identity naming strategy
- Version format
- Support URL
- Project URL
- License URL
- Privacy URL if needed
- Short and long descriptions
Shared packaging baseline
Ensure the Windows package used for distribution has a reliable baseline for:
- stable HTTPS download location
- deterministic versioned release artifact naming
- consistent silent/unattended install behavior where relevant
- upgrade/uninstall behavior suitable for channel validation
- required icons / branding assets
Shared release-output contract
Define which release artifacts are considered canonical inputs for downstream channels, e.g.:
- WinForms MSIX for Microsoft Store
- WinForms MSIX for winget, if acceptable
- any future Windows-specific installer outputs
Out of scope
- Actual Microsoft Store submission flow
- Actual winget manifest submission flow
- Client-side in-app update checks
Related tickets
Acceptance
- Shared distribution metadata is documented and agreed
- The canonical Windows release artifact(s) for downstream channels are defined
- Channel-specific tickets reference this issue instead of redefining the same metadata
- Store and winget work can proceed independently on top of this baseline
Summary
Create a shared technical baseline for Windows distribution so Microsoft Store and winget do not each invent their own package metadata, naming, and release conventions.
Motivation
Both distribution channels overlap heavily in the required metadata and packaging quality, for example:
This shared baseline should be defined once and then referenced by the channel-specific tickets.
Scope
Shared metadata
Define and document the canonical values for at least:
Shared packaging baseline
Ensure the Windows package used for distribution has a reliable baseline for:
Shared release-output contract
Define which release artifacts are considered canonical inputs for downstream channels, e.g.:
Out of scope
Related tickets
Acceptance