You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# TODO: This is too skeletal - improve it with, at least, a group generator that backs the object with a review team.
212
+
# This is very skeletal. It is enough for the tests that use it now, but when it's needed, it will need to be improved with, at least, a group generator that backs the object with a review team.
Copy file name to clipboardExpand all lines: ietf/review/models.py
+1-7Lines changed: 1 addition & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -119,13 +119,7 @@ class ReviewRequest(models.Model):
119
119
requested_rev=models.CharField(verbose_name="requested revision", max_length=16, blank=True, help_text="Fill in if a specific revision is to be reviewed, e.g. 02")
120
120
comment=models.TextField(verbose_name="Requester's comments and instructions", max_length=2048, blank=True, help_text="Provide any additional information to show to the review team secretary and reviewer", default='')
121
121
122
-
# Moved to class Review:
123
-
# Fields filled in as reviewer is assigned and as the review is
124
-
# uploaded. Once these are filled in and we progress beyond being
125
-
# requested/assigned, any changes to the assignment happens by
126
-
# closing down the current request and making a new one, copying
127
-
# the request-part fields above.
128
-
# TODO: Change that - changing an assingment should only be creating a new Assignment and marking the old one as withdrawn
122
+
# Moved to class ReviewAssignment:
129
123
# These exist only to facilitate data migrations. They will be removed in the next release.
# TODO : See if this function is still meeting the need. I removed "-reviewed_rev" from the order_by below. The whole thing may need to be operating on ReviewAssignments?
0 commit comments