Issue363

Title auto-nosy release manager(s) on release blockers
Priority wish Status resolved
Superseder Nosy List ezio.melotti, gbrandl, loewis
Assigned To ezio.melotti Topics

Created on 2010-12-06.07:53:24 by gbrandl, last changed 2010-12-15.03:00:58 by ezio.melotti.

Files
File name Uploaded Type Edit Remove
autonosy_rm.diff gbrandl, 2010-12-06.07:53:24 text/plain
issue363.diff ezio.melotti, 2010-12-15.03:00:57 text/plain
Messages
msg1872 (view) Author: gbrandl Date: 2010-12-06.07:53:24
What do others think?  Is this feasible?

(Rough patch attached; untested.)
msg1873 (view) Author: loewis Date: 2010-12-06.08:37:15
I think the patch is wrong (it needs to lookup ids from strings for users, priorities and versions), but otherwise, it is feasible.
msg1876 (view) Author: ezio.melotti Date: 2010-12-15.03:00:57
I committed the patch with a couple of changes in r87253 using the user ids instead of the names.
I then further improved the patch in r87257 to also check the previous values when they are not changed, so, if the version is already set to e.g. 3.2 and the priority is changed to release blocker (and vice versa -- priority already set to release blocker and 3.2 added), the 3.2 release manager will be added anyway. Finally I fixed a bug in r87259 that gave an error message when the priority was not set.
Attached a diff of all these changes
History
Date User Action Args
2010-12-15 03:00:58ezio.melottisetstatus: chatting -> resolved
assignedto: ezio.melotti
messages: + msg1876
files: + issue363.diff
nosy: + ezio.melotti
2010-12-06 08:37:15loewissetstatus: unread -> chatting
nosy: + loewis
messages: + msg1873
2010-12-06 07:53:24gbrandlcreate