summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAndrewMurrell <amurrel@purdue.edu>2014-03-10 20:50:51 -0400
committerAndrewMurrell <amurrel@purdue.edu>2014-03-10 20:50:51 -0400
commitf9af1121aa8b56967ad7d25ae41261ec263b5d22 (patch)
treea7dee9075b78f9c01d576f57e2ff18cc408f66a0 /doc
parentf0c03cd7fe87f054cefc97d636160eb46c95ce62 (diff)
Finished those 2 other areas.
Diffstat (limited to 'doc')
-rw-r--r--doc/Sprint1-Retrospective.md19
1 files changed, 12 insertions, 7 deletions
diff --git a/doc/Sprint1-Retrospective.md b/doc/Sprint1-Retrospective.md
index c568917..eb5403e 100644
--- a/doc/Sprint1-Retrospective.md
+++ b/doc/Sprint1-Retrospective.md
@@ -94,7 +94,7 @@ has been an impressive journey.
The entire team became familiar with deploying Rails in our rather
diverse working environments and successfully deployed a server
-instance located at demo.projectleaguer.net.
+instance located at demo.projectleaguer.net as well as on our local boxes.
## Login (back-end) {#login-backend}
@@ -110,8 +110,18 @@ place, this has been fixed).
## Tournament settings {#tourney-settings}
+Tournament settings were implemented at a basic level, instituting those
+items which are similar to all tournaments, regardless of type, orginating
+from the game model.
+
## Tournament registration {#tourney-registration}
+Tournament registration and the tournament contoller were completed which
+allowed users to join and participate in basic tournaments of several types.
+The tournament controller handled a variety of tournament related tasks,
+including creating and updating tournaments and validating tournament related
+operations.
+
## Match controller {#match-controller}
## Permissions system {#permissions}
@@ -129,12 +139,7 @@ only had it working where the tournament host would decide who won.
## Server management {#srv-man}
-The server management software interface is implemented, and working
-fine. The other modules use it. However, what we didn't implement is
-an actual *page* to edit these settings. We had this task in the
-iteration because other items depended on it. Though we did not
-implement the full story, we implemented the core reason that we
-wanted it.
+
# Not implemented