This is an automated email from the ASF dual-hosted git repository. vladimirsitnikov pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/jmeter.git
commit 1f51fd82bf7f8057a0b0c4f61ee1fcee69a06a9e Author: Vladimir Sitnikov <[email protected]> AuthorDate: Mon Oct 7 00:39:28 2019 +0300 Use rel/v${version} and v${version}-rc${rc} tags See https://octopus.com/blog/maven-versioning-explained https://cwiki.apache.org/confluence/display/MAVENOLD/Versioning Release tag should be under rel/* namespace (as per ASF board decision) Use of v${version} without dot replaced with underscores help third-party consumers as they don't have to replace dots. Neither of the articles include use of _ for separators. Technically speaking, "RC tag" is not a Maven version, however it might be a good idea to use well-known conventions. --- build.gradle.kts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build.gradle.kts b/build.gradle.kts index 1c5b5fe..df367d1 100644 --- a/build.gradle.kts +++ b/build.gradle.kts @@ -119,8 +119,8 @@ releaseArtifacts { releaseParams { tlp.set("JMeter") - releaseTag.set("v${project.version.toString().replace('.', '_')}") - rcTag.set(releaseTag.map { "${it}_RC" + rc.get() }) + releaseTag.set("rel/v${project.version}") + rcTag.set(rc.map { "v${project.version}-rc$it" }) svnDist { // All the release versions are put under release/jmeter/{source,binary} releaseFolder.set("release/jmeter")
