Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReaR releases should not mention Git in version / Dev builds should mention the Git commit hash #1362

Closed
schlomo opened this issue May 11, 2017 · 4 comments
Assignees
Labels
enhancement Adaptions and new features fixed / solved / done minor bug An alternative or workaround exists
Milestone

Comments

@schlomo
Copy link
Member

schlomo commented May 11, 2017

ATM the version string of a release (e.g. from EPEL) is Relax-and-Recovery 2.00 / Git which is confusing to customers who think that this is a development build from some git commit and not a real release.

ATM the version string of a dev build contains a date/time string and the date but not the commit hash.

I suggest to improve that so that we are more clear about the release/dev status of a package.

@jsmeix jsmeix added enhancement Adaptions and new features minor bug An alternative or workaround exists labels May 11, 2017
@jsmeix jsmeix added this to the ReaR v2.1 milestone May 11, 2017
@jsmeix
Copy link
Member

jsmeix commented May 11, 2017

I also noitced that but found no time
to investigate what the root cause is.

@gdha
Copy link
Member

gdha commented May 22, 2017

@schlomo @jsmeix This will show the effective RELEASE_DATE of an official release date. I suppose this enough for v2.1?

@gdha
Copy link
Member

gdha commented May 29, 2017

Moved the milestone to v2.2 - for v2.1 we did what we needed to do and we have no time for further corrections/modifications.

schlomo added a commit that referenced this issue Jun 22, 2017
* use git infos (rev count, hash, branch) in development version
* put resulting dist files in dist/
* not patch the working copy (removed rewrite/restore)
* use debuild to build debian package

Contributes to #1362

This is work in progress and for sure needs more attention for the OBS parts
schlomo added a commit that referenced this issue Jun 22, 2017
* use git infos (rev count, hash, branch) in development version
* put resulting dist files in dist/
* not patch the working copy (removed rewrite/restore)
* use debuild to build debian package

Contributes to #1362

This is work in progress and for sure needs more attention for the OBS parts
schlomo added a commit that referenced this issue Jun 27, 2017
* use git infos (rev count, hash, branch) in development version
* put resulting dist files in dist/
* not patch the working copy (removed rewrite/restore)
* use debuild to build debian package

Contributes to #1362

This is work in progress and for sure needs more attention for the OBS parts
@gdha
Copy link
Member

gdha commented Jul 11, 2017

I think we can close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features fixed / solved / done minor bug An alternative or workaround exists
Projects
None yet
Development

No branches or pull requests

3 participants