cemu-project_Mirror/Cemu-2024-03-05
1
0
Fork 0
Code Issues 224 Pull requests 11 Projects Releases Packages Wiki Activity

Infrastructure for shipping and auto-updating experimental releases #131

Merged
Exzap merged 10 commits from main into main 2022-08-31 06:04:09 -04:00
Conversation 0 Commits 10 Files changed 16 +261 -122
Exzap commented 2022-08-31 02:42:08 -04:00 (Migrated from github.com)
Copy link

Some changes to how version numbers are handled:

  • Experimental releases: LEAD.MAJOR-MINOR (e.g. 2.0-3, where minor is a global running number provided by the CI)
  • Stable releases: LEAD.MAJOR (e.g. 2.1)
  • If compiled without PUBLIC_RELEASE a (dev) suffix will be added to the titlebar

The current 2.0 release technically follows the version number pattern of a stable release but we'll consider that one special and experimental as well.

This PR also adds a new workflow to manually deploy experimental releases. Originally we wanted to go with automated nightly releases but that is probably a bit too chaotic. Instead the plan is to manually trigger releases when we see fit.

Auto-updating is currently only implemented for Windows. Stable releases will auto-update to stable, and experimental releases to experimental.

In regards to handling the changelogs I think we'll keep using http://cemu.info/changelog.html for stable version changelogs. And for the experimental releases we'll use a page on our mediawiki. This way anyone can add their own changes if they want to. We'll look into automated changelog generation in the future but I think for truly user-friendly changelogs a bit of manual editing is always necessary.

Some changes to how version numbers are handled: - Experimental releases: LEAD.MAJOR-MINOR (e.g. 2.0-3, where minor is a global running number provided by the CI) - Stable releases: LEAD.MAJOR (e.g. 2.1) - If compiled without PUBLIC_RELEASE a ` (dev)` suffix will be added to the titlebar The current 2.0 release technically follows the version number pattern of a stable release but we'll consider that one special and experimental as well. This PR also adds a new workflow to manually deploy experimental releases. Originally we wanted to go with automated nightly releases but that is probably a bit too chaotic. Instead the plan is to manually trigger releases when we see fit. Auto-updating is currently only implemented for Windows. Stable releases will auto-update to stable, and experimental releases to experimental. In regards to handling the changelogs I think we'll keep using [http://cemu.info/changelog.html](http://cemu.info/changelog.html) for stable version changelogs. And for the experimental releases we'll use a page on our mediawiki. This way anyone can add their own changes if they want to. We'll look into automated changelog generation in the future but I think for truly user-friendly changelogs a bit of manual editing is always necessary.
Crementif (Migrated from github.com) reviewed 2022-08-31 02:42:08 -04:00
Sign in to join this conversation.
Reviewers
No reviewers
Crementif
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: cemu-project_Mirror/Cemu-2024-03-05#131
No description provided.
Delete branch "main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?