...

1. Prepare for beta release of i18n functionality
   1. Resolve top-priority JIRA tickets 

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1907

      2. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1905

      3. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1908

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1906

   2. Merge `i18n-sprint` branches into their respective `master` branches
      1. https://github.com/vivo-project/VIVO/tree/sprint-i18n
      2. https://github.com/vivo-project/Vitro/tree/sprint-i18n
      3. https://github.com/vivo-project/VIVO-languages/tree/sprint-i18n
      4. https://github.com/vivo-project/Vitro-languages/tree/sprint-i18n
   3. Update documentation
      1. User documentation - As a user, how do I use the new i18n functionality?
      2. Adding a new language documentation - How do I bring a new language to the suite of available VIVO languages?
      3. Configuration and Activation documentation - As a site administrator, how do I configure and enable one or more available VIVO languages?
      4. Upgrade documentation - As a site administrator, how do I upgrade my site and data to use the new i18n functionality?

Stand-up Reports

Template

[VIVO i18n Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Blockers:
  {brief textual description}

Reference

i18n Update list to be merged to master

...