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

Naming for testing builds #3

Closed
hugbug opened this issue Jun 17, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@hugbug
Copy link
Member

commented Jun 17, 2015

Testing builds had svn revision number in their names, for example 15.0-testing-r1283, where r1283 is the revision number. GIt being a distributed VCS doesn't have such revision numbers.

However we still need something to distinguish the testing releases. At best the naming scheme should remain unchanged in order to provide compatibility with existing installations. This is necessary because the built-in update routine relies on existing naming scheme.

Version names for testing releases are automatically generated during make process. That's coded in Makefile.am.

@hugbug hugbug added this to the Migration to git milestone Jun 17, 2015

@hugbug hugbug added the meta label Jun 17, 2015

hugbug added a commit that referenced this issue Jun 17, 2015

#3: implemented naming for testing builds
Naming:
 - for master-branch: no suffix;
 - for develop-branch: suffix “rXXXX”, for example “16.0-testing-r1257”;
 - for other branches: suffix “rXXXX (<branch>)”, for example
“16.0-testing-r1257M (migration-naming)”.
@hugbug

This comment has been minimized.

Copy link
Member Author

commented Jun 17, 2015

Naming:

  • for master-branch: no suffix;
  • for develop-branch: suffix “rXXXX”, for example “16.0-testing-r1257”;
  • for other branches: suffix “rXXXX (branch)”, for example
    “16.0-testing-r1257M (migration-naming)”.

@hugbug hugbug closed this Jun 18, 2015

hugbug added a commit that referenced this issue Jun 20, 2015

#3: corrected a comment
For naming testing releases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.