HI, > I don’t think we need to change the release tag hash. Tag ‘dubbo-2.6.2’ has > never changed, so the source release, binary release and the release tag are > still in consistent to each other. Be aware that CHANGES.md only exists in > the ‘2.6.2-release’ branch, a branch we used for release purpose, it serves > for the release process but not bounded.
As tags are mutable in git it best to specify the hash in the release vote email (ie afab04c). Thanks, Justin
