Hide Forgot
Description of problem: Unit tests fail because old version number (2015.12) is sepcified in setup.cfg. Version-Release number of selected component (if applicable): How reproducible: Run unit tests.
Updated version # to 2015.1.3 in setup,cfg
Could we have a link to the failure? Also, is it enough to s/2015.1.2/2015.1.3/ ? Shouldn't we bring in all the changes that happened between 2015.1.2 and 2015.1.3 as well?
posted a link in private considering the commits from 2015.1.2 to 2015.1.3 - I suppose that you with Erno as owners should pick up what do you want to see in downstream version (everything/some specific patches/nothing). 04e5233 Open Kilo 2015.1.3 0303c5c Merge "Download forbidden when get_image_location is set." into stable/kilo d71bae6 Updated from global requirements 786ecd1 Merge "Catch NotAuthenticated exception in import task" into stable/kilo 15e34b5 Catch NotAuthenticated exception in import task 2499162 Download forbidden when get_image_location is set. 5bebd51 Cleanup chunks for deleted image if token expired 9beca53 Prevent image status being directly modified via v1 6644042 Merge "Fix Request ID has a double 'req-' at the start" into stable/kilo f659722 Merge "return request_id in case of 500 error" into stable/kilo f732d0c Updated from global requirements 0b27935 Fix Request ID has a double 'req-' at the start 30f0c40 return request_id in case of 500 error 53fc470 Updated from global requirements eb99e45 Don't import files with backed files c062362 Merge "Allow ramdisk_id, kernel_id to be null on schema" into stable/kilo 752bb46 Bump stable/kilo next version to 2015.1.2
Hi David, I do not think that we should backport some of the commits that were committed between 2015.1.2 and 2015.1.3. If we tell users that we ship 2015.1.3, then we should give them that - plus our own patches on top of that. I think we should really update the package (dl the 2015.1.3 tarball, update the checksum etc.), not just manually edit the setup.cfg.
No objection :)