Include version tags in the repository

[JonnyJD]

I am a bit confused about the versioning of xrdp.

There are no version tags in this repository. The old (sf) repo had at least a v0.4.1 tag.
So it is difficult to match versions to commits.

Then I am also unsure if 0.6.0 is the last release version (a download on SF exists) or if there is a 0.7.0 version, since there is a 0.7.0 branch that didn't receive any changes for 9 month, but there are lots of changes in master.

[speidy]

Master brnach is the updated branch.
On Jun 10, 2013 6:43 PM, "Johannes Dewender" notifications@github.com
wrote:

I am a bit confused about the versioning of xrdp.

There are no version tags in this repository. The old (sf) repo had at
least a v0.4.1 tag.
So it is difficult to match versions to commits.

Then I am also unsure if 0.6.0 is the last release version (a download on
SF exists) or if there is a 0.7.0 version, since there is a 0.7.0 branch
that didn't receive any changes for 9 month, but there are lots of changes
in master.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/77
.

[JonnyJD]

Not sure why your answer is relevant to my question. I know the master branch is the latest. That part of the question was rather about why there is a 0.7 branch that doesn't move forward, when there is no 0.7 release.

Usually you create a stable branch for a major or minor version to make patch releases while making big changes in the trunk/master. This branch can already be created before the actual release of that version, but there is not a single commit that is in the 0.7 branch that isn't in master. This begs the question if that was intended as a "release tag".

PS/EDIT:
Having a tag for v0.6 would also make it easier to see if there are actually changes between 0.6 and the 0.7.0 branch. The release and the branch are created about the same time.