Automate the release process #366

New issue

Open

opened 2022-01-03 07:01:49 -06:00 by Youw · 1 comment

Youw commented

2022-01-03 07:01:49 -06:00

(Migrated from github.com)

Kind-of related to #315.

Right now there is a set of manual steps that needs to be done for each release.
As a human, the person who performs those steps can make a mistake and f**k-up the release (Presisely what I did when tried to release a 0.11.1 - forgot to update the version file. That's why we have 0.11.2 right after 0.11.0).

That process better be fully automated (except the release NOTES - those better be filled up manually).

I don't have a final idea how to do so, but it better be done rather sooner than later.

Kind-of related to #315. Right now there is a [set of manual steps](https://github.com/libusb/hidapi/blob/master/HACKING.txt) that needs to be done for each release. As _a human_, the person who performs those steps can make a mistake and f**k-up the release (Presisely what I did when tried to release a 0.11.1 - forgot to update the version file. That's why we have 0.11.2 right after 0.11.0). That process better be fully automated (except the release NOTES - those better be filled up manually). I don't have a final idea how to do so, but it better be done rather sooner than later.

Youw commented

2022-05-08 12:01:23 -05:00

(Migrated from github.com)