You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You could use GitHub releases when new stable releases are made. It would make it easy for users to subscribe to something to get notified of new releases of SCEPman and Certificate Master.
Idea:
Separate releases for Certificate Master and SCEPman.
Include changelog for the released version only in GitHub releases.
I'm not currently aware of other ways to get notified of new releases.
The text was updated successfully, but these errors were encountered:
When using releases, the URL of the ZIP changes with every release. For the WEBSITE_RUN_FROM_PACKAGE update mechanism, we need a fixed URL (for each channel). So we cannot use GitHub releases for this and we need still need to have the ZIPs in GitHub.
Therefore, the GitHub releases would just be there as a mechanism to have a change log with notifications. This seems unnatural to me, although of course I see advantages, e.g. it would be a place where people expect the releases.
Therefore, the GitHub releases would just be there as a mechanism to have a change log with notifications. This seems unnatural to me, although of course I see advantages, e.g. it would be a place where people expect the releases.
I'd say that this would still provide the value I ask for here. Then one can use either GitHub natively, or use <repo>/releases.atom in a RSS reader. No need for custom logic for the consumers.
Example /releases.atom for the PowerShell repo, which one can put straight in Feedly or other RSS readers:
The changelog does not seem to have a RSS feed.
You could use GitHub releases when new stable releases are made. It would make it easy for users to subscribe to something to get notified of new releases of SCEPman and Certificate Master.
Idea:
I'm not currently aware of other ways to get notified of new releases.
The text was updated successfully, but these errors were encountered: