Publish release tags

[jason1987d]

I ask as I am attempting to package this for a Linux distribution, however they require both to compile from source, and for versions to be stable (i.e. not a git commit). There are tags present, however the latest is from 2016.

[okybaca]

Yes, that would be more than usefull!
Already requested at #348.
Since there are version numbers still, they should be tagged.
Version 1.940 apparently started with this commit.

About releases - Github Docs

[okybaca]

what tagging strategy would you suggest? tag the old version with the latest commit before version change? what about new versions? would there be a place like 'stable'? what version would you use for the distribution? latest? previous?

[jason1987d]

I'm not sure I'm fully qualified to answer all your questions as I am not a yacy developer but rather a distribution packager, but with voidlinux we like stable-ish releases (i.e. no rc, beta, alpha or git commits) so something with standard semver like 1.940.x should be fine.

[okybaca]

OK, thanks! For a longer time I was thinking, why YaCy doesn't have a developement and stable branch? Stable package could at least be signed, which is verified by YaCy Update. Developement could be the one auto-generated by github. that may be even some reason for why so many peers stick to particular old version as of: https://yacystats.de/d/edquz3nqqr11cc/yacystats-de-dashboard?var-Interval=$__auto&from=now-7d&to=now&timezone=browser&var-Peers=$__all&refresh=5m&viewPanel=panel-73 * 1.924 is latest released windows package * 1.930 is last released mac package @Orbiter, could we please tag the releases, so these could be stable points allowing the various distributions to make the packages?

[okybaca]

to keep things realy simple (and don't get overheaded by all these release processes), we maybe could:

• tag the historical major version releases, where the version number changed (it's usually when switching to newer solr)
• optionally: for a packaging purposes in the linux distributions (which need the release tag instead of a commit number) assign a minor version tag (such as 1.941 or 1.940.1) in the latest version of yacy -- skiping this step, that "stable point" for packaging systems distribution would be the previous major version

impact:
yacy could be distributed using various packaging systems and therefore the adoption of yacy could be larger and more easy for some platforms

@Orbiter , what do you think?

[okybaca]

So these would be first and last commits of untagged releases:

version	first commit	last commit
1.940	8eb0d49
1.930	6bd5f49	b8417e5
1.926	e931b80	376bcfd
1.925	7c86826	56aa23a
1.924	32ca669	ed97892
1.922	bb7d836	baad56d
1.921	6fe7359	dddf593

@Orbiter, could you please tag the old ones?
and let's suppose, 1.930 is a base for various distributions then, and 1.940 being the 'latest/development'.
or, make some point tagged 1.940 and go for 1.941 version as development.