My apologies - I don't know where that SHA came from, my repo has the correct one. I will push a 1.3.1 release request now. Bob On 12/14/18 3:03 AM, Tony Breeds wrote:
On Fri, Dec 14, 2018 at 02:28:19AM +0000, Singh, Niraj wrote:
Hi Bob,
Verified the info about the latest tosco-parser release 1.3.0, I can see my changes in the commits [1]. But after downloading the zip file under release 1.3.0, I didn't found my changes that was in [2]. Your request for 1.3.0 was against the SHA 0c77377
Look here: [tony@thor tosca-parser]$ git lol 1.2.0..1.3.0 * 0c77377 (tag: 1.3.0) Move extension tests to where stestr can find them * f2ca5eb Merge "Use stestr instead of testr" |\ | * 803b2a8 Use stestr instead of testr * f231b27 Merge "Fix error using get_attribute with HOST in case of setting host relationship in "long" format." * c08022d Fix error using get_attribute with HOST in case of setting host relationship in "long" format.
However that SHA you requested was well behind origin/master
[tony@thor tosca-parser]$ git lol 1.3.0..origin/master * e0c67af (HEAD -> master, origin/master, origin/HEAD, gerrit/master) Merge "Add py36 to tox.ini and setup.cfg" |\ | * 4bdad8e Add py36 to tox.ini and setup.cfg * bfed830 Merge "Add reservation policy support" |\ | * fd3c74b Add reservation policy support * 466a489 Merge "Change openstack-dev to openstack-discuss" * f90efb1 Change openstack-dev to openstack-discuss
The chnage you want is in that range.
You can request a new release for 1.3.1 or 1.4.0 whichever is the appropriate semver via the same method.
Yours Tony.