backdating checkins to the future should not be allowed
Bug #1016204 reported by
Thomas Berezansky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.5 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Instead of trying to teach SIP2 to not backdate checkins to the future the branch below teaches the circ module to treat them as not backdated at all.
Changed in evergreen: | |
status: | New → Triaged |
Changed in evergreen: | |
milestone: | none → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → 2.5.0-alpha |
Changed in evergreen: | |
milestone: | 2.5.0-m1 → 2.5.0-m2 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha1 → 2.5.0-alpha2 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha2 → 2.5.0-beta1 |
Changed in evergreen: | |
milestone: | 2.5.0-beta1 → 2.5.0-rc |
Changed in evergreen: | |
milestone: | 2.5.0-rc → 2.5.1 |
Changed in evergreen: | |
milestone: | 2.5.1 → 2.5.2 |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 2.5.2 → 2.6.0-alpha1 |
Changed in evergreen: | |
status: | Triaged → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
no longer affects: | evergreen/2.4 |
To post a comment you must log in.
Changed the title, since this code isn't really SIP specific, and hopefully the change will cause it to get more eyes.