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
Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
cgdb's release archives that include the files generated during autorelease.sh could be uploaded here. That way, anyone with write permissions to the cgdb repository can run the entire release process. There are also some other nice-to-have features like automatically generating release notes from the commits and pull requests. Plus, people familiar with finding package releases on github will find cgdb releases in the expected place.
Changing the location of releases may impact package maintainers at the various distros that maintain a cgdb package. For the sake of backwards-compatibility, I can keep the cgdb.me/files archives up for however long it makes sense to do so.
Posting to get feedback on the idea. If people agree with the suggestion, I'll go ahead and migrate some recent releases over to the new process and submit a PR for any changes that would be required for autorelease.sh / release-todo.txt, as well as the website changes on cgdb.github.io.
The text was updated successfully, but these errors were encountered:
Github has a nice facility for producing releases of a package: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
cgdb's release archives that include the files generated during autorelease.sh could be uploaded here. That way, anyone with write permissions to the cgdb repository can run the entire release process. There are also some other nice-to-have features like automatically generating release notes from the commits and pull requests. Plus, people familiar with finding package releases on github will find cgdb releases in the expected place.
Changing the location of releases may impact package maintainers at the various distros that maintain a cgdb package. For the sake of backwards-compatibility, I can keep the cgdb.me/files archives up for however long it makes sense to do so.
Posting to get feedback on the idea. If people agree with the suggestion, I'll go ahead and migrate some recent releases over to the new process and submit a PR for any changes that would be required for autorelease.sh / release-todo.txt, as well as the website changes on cgdb.github.io.
The text was updated successfully, but these errors were encountered: