tags please

[greyltc]

Hi, would it be possible to tag some stable commits or generate some releases here? Packaging becomes challenging without this.

[dsharlet]

Can you share any details about what the project you are trying to package is, and what issues you've run into with XNNPACK when trying to do so that tagging would fix?

We have several large dependencies (some of which we manage ourselves), and we haven't seen issues from just periodically updating the git commit for the XNNPACK dependency.

My concern is that even if we did tag releases, that we wouldn't be adding any value over just grabbing commits when convenient for you. If we were getting bug reports that required patching older branches, that would motivate tags/release engineering, but I'm not aware of any examples of that happening.

[greyltc]

For example, the build of the python-pytorch package on Arch Linux refetches and rebuilds XNNPACK every time in the pytorch build process because it's not really possible to package XNNPACK separately since a prospective XNNPACK package maintainer can't really know what should or shouldn't be packaged since this repo has no tags pointing to stable releases.