Page History

...

1. Community questions
   1. Updates? "Site admins" unable to add People (email)
2. Working towards 1.12
   
   1. To be reviewed 

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

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

   2. Documentation needed

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

   3. 1.12 release planning
      1. Code freeze once i18n tickets are merged into the sprint-i18n branch (when?Jan 20th)
      2. Sprint to test merge of sprint-18n into master: week of Jan 25th
      3. 1.12 release candidate #1: Feb 1st
         1. Two week RC-1 testing period
         2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      4. Do we want the `war` install in 1.12? -

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

3. Tickets that should be close to merge

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

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

4. Post-i18n priorities
   1. VIVO-in-a-box
   2. Messaging
   3. Moving Scholars closer to core - next steps
5. Moving Data Ingest Task Force forward

...