Hi Justin, > Hash for the release tag: > afab04c53edab38d52275d2a198ea1aff7a4f41e
It’s included in the initial vote email. > On 16 May 2018, at 10:44 AM, Justin Mclean <jus...@classsoftware.com> wrote: > > 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
