Versions Compared

Old Version 6

changes.mady.by.user Alexander (Sacha) Jerabek

Saved on

compared with

New Version Current

changes.mady.by.user Brian Lowe

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Status of In-Review tickets

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=14416
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes 

Link on DuraSpace Wiki:

https://wiki.lyrasis.org/display/VIVO/2021-02-23+-+VIVO+Development+IG

Attendees

  1. Brian Lowe
  2. Benjamin Gross
  3. Nicolas Dickner
  4. Georgy Litvinov
  5. Benjamin Kampe
  6. Michel Héon
  7. Huda Khan
  8. Ralph O’Flinn
  9. Don Elsborg
  10. Alexander J. Jerabek
  11. William Welling

Notes

  1. Slack questions
  2. Releasing 1.12 alpha
    • Release process
      • Michel: will there be a tag?
      • Ralph: there is an alpha tag (rel-1.12.0-alpha-1) ; typically 2 weeks after RC; then, it will be merged in main as rel-1.12.0. Usually won’t create an artifact for the alpha
      • Brian: could people be more inclined to test if there was a .war file to download?
      • Benjamin: best to provide options
      • Ralph: previously, source code + artifacts for the installer, so will keep it that way.
    • a) blockers
      • VIVO-1956
        • Brian : two PR to test (to make initial RDF files more consistent) ; test should be easy, no functional changes ; queries are provided to help testing
        • Added readme file
    • b) Deployment and developer workflow
      • Brian: William Welling has added an option to build where you can specify if you have a Catalina home variable pointing to your directory, it will copy the .war to Tomcat : https://github.com/vivo-project/VIVO/pull/224
      • William: it’s a basic Maven profile that copies the war file for the user.
      • Brian: not tested yet. Michel has issues.
      • Michel: UQAM problem is that deployment of VIVO home is now done at the moment of deploying the war file ; which creates a dependency between the code and the installer of VIVO ; so it makes the development of an independent installer impossible ; it also makes impossible to configure runtime.properties before starting Tomcat.
      • William: it was the case before, but the process now allows to configure runtime.properties, which would allow an overlay install strategy such as UQAM. However, there is a caveat: you’ll need to create a digest file for the home directory ; this needs to be documented. 
      • Don (in chat) Moving forward I would have a digest file checked into source code control and embedded with the rdf directory in our 3rd tier
      • Michel: this new procedure has to be documented as soon as possible, as UQAM and UQAM partners current install processes are blocked.
      • William: it is possible to keep on using UQAM installer, with some configuration.
      • Michel is unsure whether it would work with overlays ; thinks it’s bound to cause problem with i18n installs
      • Ralph: might not be as bad as it looks ; we could put up documentation for the alpha release, so we can assess it.
      • Michel: there could be a quick fix. When Tomcat starts, if VIVO home is already there, it shouldn’t be erased ; it could be in runtime.properties or developper.properties
      • William: those files are in the VIVO directory, so it’s a chicken and egg problem.
      • Michel: that’s bad  practice; config files should be there before starting the application.
      • Brian: the goal was to make it easier for people who have a simple install process. Michel is right that it seems backward for more complex install processes. However, it looks like the digest file William was talking about would play the role of that config file. So the digest file could be used as a switch for a custom installer.
      • Michel: it’s too early to deploy this in the release ; more reviewing has to be done on that feature.
      • Brian: is it easy to revert?
      • Ralph : it has been checked in, there’s code on top of it, would be hard to revert it. There’s 4 weeks of testing and tweaking left before the release. It’s not that much code, it’s still possible to keep both approaches.
      • Michel: do we have to just touch the digest file?
      • William: it’s the checksums of the content of the file ; you just have to write it the first time.
      • Brian, let’s schedule a meeting to discuss this  : Thursday 10 EST.
  3. New developments
    • a) VIVO-1962
      • Brian: long needed feature ; PR in review. General idea is you can create a query with specific arguments (MostSpecified type, etc) and it will use DESCRIBE to spot and delete the corresponding triples.
      • Georgy: it’s working, even though some cleaning might be needed
      • Brian: options could be used in order to generate more complex queries

Draft notes on Google Drive

...