mv migration file from test/dummy
discuss user streamlining associations
no more delivering a message by default. a message is a draft by default, unless the user specifically asks to send the message. And even then, if there are no recipients, the message will remain a draft.
So to summarise: a message will be sent if: a user selects to send it and there are recipients
message#sent_at is set when sending a message. once sent?, message cannot become a draft again
mailbox actions [wip]
mailbox#empty_trash!
mailbox: testing that we can delete a draft message
no real need for draft if we are using sent_at
spliting the messages controller into a second one for the mailboxes list view
rm links to assets for now. the test suite looks at the layout file in the dummy app
Gemfile: adding haml for :test group or the test suite cannot find .haml views
rm mocha
not sure if needed so removed for now
starting on features tests
Merge branch 'feature/mailboxes'

* feature/mailboxes:
  starting on features tests
  not sure if needed so removed for now
  rm mocha
  Gemfile: adding haml for :test group or the test suite cannot find .haml views
  rm links to assets for now. the test suite looks at the layout file in the dummy app
  spliting the messages controller into a second one for the mailboxes list view
  no real need for draft if we are using sent_at
  mailbox: testing that we can delete a draft message
  mailbox#empty_trash!
  mailbox actions [wip]
  message#sent_at is set when sending a message. once sent?, message cannot become a draft again
  no more delivering a message by default. a message is a draft by default, unless the user specifically asks to send the message. And even then, if there are no recipients, the message will remain a draft. So to summarise: a message will be sent if: a user selects to send it and there are recipients
  discuss user streamlining associations
  mv migration file from test/dummy
Merge branch 'master' of github.com:elle/discuss

* 'master' of github.com:elle/discuss:
  Adjusting update to time.zone.now to allow for this to be used within an app with multiple time zones without causing problems.