releases tagged, but not marked as released

[beadon]

It appears that the https://github.com/rakshasa/libtorrent/releases/ do not have any releases publicly shown. However, there are tags set for these versions, and drafted release notes.

I believe @rakshasa you just need to update the release with a couple clicks so the release for this lib is available.

screenshot attached.

[rakshasa]

The releases are in the rtorrent repository, and I don't really plan on keeping any separate release notes for libtorrent.

[beadon]

As you know - the software is currently released in 2 parts, the library (libtorrent) and the client (rtorrent). I absolutely don't want to generate more work, or duplicate effort.

If there are only ever releases of rtorrent, and the releases come from rtorrent, we need a way of also releasing libtorrent with the correct version numbers. Since this will get packaged up and used by other clients, it's important the versioning is consistent, the rtorrent build requires it.

Proposal:
Would you be willing to just mark each libtorrent version as released ? This could be done first, before even writing notes in the rtorrent release in the other repo.

A note in the release notes for libtorrent would point readers to the rtorrent release page, easily copy+pasted. This would do 2 things - 1 kick off the script and 2. make it clear to other packaging people that the version is real, not just a tag on a repo.

[rakshasa]

I would prefer not to add maintenance overhead to the core libtorrent/rtorrent repositories, as I am the sole maintainer.

Building packages for various distributions should be handled in an external repository that can be maintained by others.

[beadon]

Ok. I am going to have to rethink how to build packages this - becuase GitHub revolves around the main repo being used to build the packages and stick them on releases -- the triggers in the PR are all built on the tags for this repo.

For this request -- for a simple package maintainer who is seeing this repo for the first time could you just mark the tagged versions as releases ? This will not build any packages for you, it just communicates an official release, and a point-in-time for the code. You have the tags in place, as long as these are at the right places, the GItHub release creation prompts should just accept the existing tags, and you could fill in a subject of the release which is the same as the tag.

[beadon]

Could you ( @rakshasa ) regularly mark the tagged versions in libtorrent as released ?