...
- Community mailing list
- ...
- Sprint planning: 1.12
- Planning meeting: Friday, Jan 22 @10am ET
- Merged!To be reviewed
Benjamin Gross / Brian Lowe : any final comments?Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1918
- Documentation needed
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1914
- Bugs to be fixed
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1910 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1929
- 1.12 release planning
- Email of schedule to vivo-community
- Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
- Sprint to test merge of sprint-18n into master: week of Jan 25thFeb 8th
- 1.12 release candidate #1: Feb 1st15st
- Two week RC-1 testing period
- For each subsequent RC-2 (if required), adding another two weeks to the schedule
- Do we want the `war` install in 1.12? -
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1443 - Next steps?
- Tickets that should be close to merge
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1652
- Post-i18n priorities
- VIVO-in-a-box
- Ingest / Kafka
- Messaging
- Moving Scholars closer to core - next steps
...