...
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
As Andrew is leaving Zoom links are going to be changed.
Significant milestone is going to be achieved with the merging ticket 1958. Brain reviewed and tested new changes. Ralph was doing sanity checking. Checked new building process. Checked on multiple systems like Windows, Mac and Linux, multiple browsers. Ralph is working on checking i18n.
1. I18n Pull requests
Andrew asks about pull requests.
Either merge PR today or get some feedback on them. Some tickets on hold because of them.
Ticket 1958 should help with testing new functionality.
No code review expected at this point. There already have been code reviews.
Need basic testing.
William will try to test, at the same time VIVO needs a lot of resources for testing.
2. Digest file
Didest file is now being created. The idea is now with 1959 we copy war file in tomcat. When tomcat starts VIVO Home directory got populated with war contents. As a part of that VIVO creates an md5 base file. With tomcat restart digest file is being read to find changes since last startup with files in VIVO Application. If files in war and on disk differ then files in home directory rewrites only if they were not changed. Digest file gets updated every time VIVO restarts.
On restart it recreates files map with md5 and date information.
The only untouched files are getting overwritten.
If somebody want to look at this - you are welcome.
Benjamin says it works good.
3. Tickets to be closed
Ticket 1802 Nicolas says it is expected behaviour. Ticket should be closed.
4. Putting out alpha release
We want to ensure users can upgrade. Upgrad should works with i18n and without it.
People in both scenarios should have upgrade instructions without issues.
All 1958 dependencies should be resolved shortly.
Merge all by the end of the week.
Reshuffling of RDF is ok for now as it doesn’t create any problems.
Given the pace of things Andrew wont be able to push Alpha and RCs.
Timing, Process, Communication with community
Release on monday or next week ? Release alpha by the end of next week.
Send announcement for the community that aplha is ready, test it.
Encourage testing! A day for extensive testing RCs after internal testing alpha.
Advanced role management
VIVO-1436 It was targeted against main. Could have merge conflicts after 1958.
It could not be merged in 1.12 at this stage.
Plan for merging after 1.12, maybe release in 1.13
Use travis for testing more.
Moving scholars closer to core
Publish docker container on docker hub to simplify using VIVO.
...