Kai Koehne (20 March 2018 09:34) > I would rather create a task in JIRA for the review itself, with priority 1 > and appropriate fixVersion. Any subsequent findings could be made subtasks of > this task. > > This automatically makes the API review part of the blockers list, and makes > sure > everyone understands that this needs to be done before a release.
Good idea - I'll add a --task[-number] option to the api-review-gen script; if you open that bug and tell me its ID, I'll exercise this option when next I run the script (hopefully later today) to pick up all the changes folk have made in response to reviews so far, How will the fact that I abandon reviews once they have +2 (or we ship a release) bear on that task's view of them ? Eddy. _______________________________________________ Releasing mailing list Releasing@qt-project.org http://lists.qt-project.org/mailman/listinfo/releasing