...

1. Comments? Observations?
2. Present status
   1. Several tickets in-review

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

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

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

   2. Need to rebase:

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

3. Remaining to be done
   1. Documentation tickets

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

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

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

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

   6. Need to verify if this is still an issue:

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

4. Prior to merge into 'master'
   1. Documentation
   2. Upgrade testing

Notes 

1. New ticket needed for Spanish and Portuguese as a supplement to:

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

2. Upgrade testing:
   1. William Welling to see if TAMU could verify non-breaking upgrade of non-i18n installation
   2. Michel Héon to verify upgrade to i18n branch
3. Plan for rolling out the i18n work/release
   1. Complete identified blocker tickets
   2. Merge sprint-i18n branches into respective master branches
   3. Publish i18n-beta to community from master branch
   4. After period of community testing... release 1.12.0