Fix storage of rounds for new puzzle creation

[turbot] / TODO

diff --git a/TODO b/TODO
index edbafc5489a9de38a7900716e07846a403339262..ca8ec0e5311135c6e8a932c9e61104d9a33028a2 100644 (file)
--- a/TODO
+++ b/TODO
@@ -3,17 +3,6 @@ Recently-proposed ideas (not yet prioritized)
 • Set-up an announcements Slack channel that's auto fed by email to a
   particular email address.
 
-Low-hanging fruit
------------------
-
-[These are not highest priority, but are so easy that they are worth
-not delaying until after bigger features below.]
-
-• Fix /puzzle dialog to reject a puzzle with the same URL as an
-  existing puzzle.
-
-• Make /solved clear the state string for a puzzle.
-
 Round management
 ----------------
 
@@ -100,16 +89,6 @@ Un-prioritized items
 
 • Add support for recording/displaying those who have current roles
 
-• Decide a good plan for audio/video calls for puzzles and integrate
-  that into Turbot.
-
-• Inspect the CloudWatch logs for our Turbot AWS Lambda during the time
-  period of the active hunt, (October 24-31), find and diagnose any
-  errors that occurred during that period. Users reported seeing
-  "Trouble connecting" (probably during new-puzzle dialog submission)
-  as well as "dispatch_failed during /state command (perhaps due to a
-  state string that was very long).
-
 • Think about some way to express solve priority
 
 Lower priority