TAG August 27 2021

Zoom Link: https://zoom.us/j/968367412

Attending

• Rosie Le Faive
• Seth Shaw
• Don Richards
• Bethany Seeger
• Jared Whiklo

Agenda

Old Business / New Business

• Branches in Islandora

Notes

General question about how to run meetings, organizationally

Branches in Islandora

• What modules do we consider islandora
• https://docs.lefaive.ca/w/index.php/Repository_Diagram
• https://docs.google.com/spreadsheets/d/1rC9EVXIxZQIUxGgquCytlDFUoZgCnow0uuxfBiRGC5s/edit#gid=0
• Drupal has things like 2.0-dev and 3.0-dev
• change github branches named 2.x, 3.x
• composer would use dev-2.x for development and 2.0.0 for release
• https://github.com/composer/composer/blob/master/doc/articles/versions.md
• We could have a 2.x-dev and apply tags as we have releases
• We have some tests, just not for everything.
• Don is working on BeHat stuff for ISLE now.
• Should we ask committers to start adding tests when they add fixes/features to Islandora things
  • tricky balance between getting in material and having good test coverage
  • at least having a test suite to run against (consisting of existing tests) that must pass before a PR is accepted
• Composer 2 and moving to it
• Ideas
  • branch from 8.x-1.x branch from the 2.0.0 tag
  • do we leave 8.x-1.x? Some might get burned by branches disappearing.
    • maybe give notice that these branches are going to disappear
    • Ansible/galaxy will need to be updated
• How do we do dev and releases on the same branch, where the release doesn't have the "dev-" branches in it, but rather uses tags.
• maybe easier to lock Islandora 2.x branch to have all dependencies use a tag (no "dev-") as versions in requirements. Then when folks are working on modules they will need to be careful as to what they put on that. Breaking changes should version number up and require more testing on the Islandora. A dev could work on a branch and then make it "live" by tagging it with the next version.
• how would this affect ISLE and Ansible. ISLE is driven by the composer.json file.

Outputs:

• We should document this idea, refine it. Make a work plan. Run past tech.
• Create documentation for developers on how to work with their modules to meet our expectations for version.
  • have them follow this as well https://www.drupal.org/node/3108648
  • noting our requirement for explicit dependencies in composer files

Are the java artifacts affected by this or needing any change? Probably not.

In the future we could see maintaining more than one branch (of dev), but right now there's just 2.0