Thanks Xiao Chen for the new rev.
Hi Akira Ajisaka, Brahma Reddy Battula, Haohui Mai, Kai Zheng, Vinayakumar B,
Currently a release is done in a few steps:
1. create release branch,
2. add additional important fixes
3. change the hardcoded release name right before the final build such as removing "_SNAPSHOT" from "x.y.x-SNAPSHOT"
For step 3, the release name is involved in lot of pom.xml files all over the places. Ideally we could have a single place to hold the release name variable, and refer it in all relevant pom.xml files, so whenever we need to make a change, we only change the single place. But we did not do that, because it's not as straightforward as defining a constant in a computer language.
For this jira, I'd propose to add another step to the release steps
4. change the hardcoded year in the several involved files.
Although this is similar to what's done in
HDFS-8149, what I would like emphasize is, adding step 4 to the release process, as a guideline, which should be documented somewhere.
As a matter of fact, step 3 and step 4 could be done by a script altogether in the release process.
What do you think?