triplem commented on issue #908: Fix release build process tooling URL: https://github.com/apache/couchdb/issues/908#issuecomment-338374736 Just leaving my w$ here. It is good practice to keep the current version in a file in the project (eg. version.mk), as examples see Java builds using Maven or Gradle. In Nodejs this is common practice as well. I guess that the version.mk should be used as this single source of truth for the version of couchDb. This information could then be used in the Makefile to bump the version eg. by using a tools like https://github.com/peritus/bumpversion (python) or https://github.com/fsaintjacques/semver-tool (bash). Then this information should be used in the Makefile. No specific target for RC necessary then, just one to create the tarball. Some of the tools do tag the girls repository as well after a bump, so that the tags and releases in GitHub as well (which I think can be easily done in the Makefile as well). I have looked into the releng config but have to admit, that I do not have a clue on how to adopt the version in there. Probably via a parse/replace? Does this help you already?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
