There is no versioning

[Andromeda606]

What version is used in the repo? Which is the stable version? We don't have detailed information about these.

I think a release like version 1.0 should in Github be released and a release should be published.

[Benjamin-Loison]

Sorry for the blabla, just me thinking out loud, if you are interested to figure out how I work and how you may help me work better.

Maybe it is just laziness, but I don't like defining versions (I have too much suffered of maintainers committing, but not defining a new version (maybe because contrarily to here in some programming languages there is a build step necessary to end up with a binary, quite like Docker here in fact), Termux (possibly with its extensions) is such an example). I like the idea of having versions defined as commits, as it is done in:

YouTube-operational-API/index.php

Lines 294 to 300 in 6750e3d

	$version = 'an unknown version.';
	$ref = str_replace("\n", '', str_replace('ref: ', '', file_get_contents('.git/HEAD')));
	$hash = file_get_contents(".git/$ref");
	if ($hash !== false) {
	$version = "version: <a href=\"https://github.com/Benjamin-Loison/YouTube-operational-API/commit/$hash\">$hash</a>";
	}
	echo "<br/><br/>This instance (" . SERVER_NAME . ") uses $version";

Let me know if it is a blocker for #336. If it is, then let me know if we can't define version by commit instead.

Note that the only flaw I am aware of is that ideally each commit should not break the features, but sometimes to ease big changes, I proceed with small commits which may break the features. Most of time in such cases I push multiple commits at once to not break the features if someone git {clone,pull} at an arbitrary time. I guess that it is the purpose of branches and pull requests, but I admit not using them carefully yet as at least until now it has not disturbed much users.

[Benjamin-Loison]

Related to #162.