Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
Agenda
What are details that we should articulate related to a proposed 4.7 LTS?
- Gradle as build tooling
- Possible messaging memory leak?
- Tickets/PRs that need merging:
- Ben Pennell's Import Export of Versions PR https://github.com/fcrepo4-labs/fcrepo-import-export/pull/109
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- Intent and ground rules for LTS:
- How long will the LTS be maintained? When do we stop supporting it?
- Consensus: 3 years
- Jared Whiklo: smaller institiutions need reassurance that investments in technology will have some known duration.
- There are still people using Fedora 3.7.x
- Jared Whiklo: smaller institiutions need reassurance that investments in technology will have some known duration.
- Esme proposed an annual review of who is using it and semi-annua/annual commitments to maintain the LTS
- Jared Whiklo: won't instill confidence in smaller institutitions if a version can go away when committers decide we are no longer interested in maintaining.
- Esmé Cowles : yes, making explicit the general timescale for maintainence is important in any case.
- Consensus: 3 years
- What will be maintained?
- Bug fixes
- Migration paths to later versions?
- No commitment to backporting features
- ongoing JVM support?
- Doesn't sound like fun, but java 8 is approaching end of life.
- To be evaluated in the annual review: Question depends of whether users have options.
- Perhaps we should not necessarily commit to support Java 9. But will support it to the extent that there is community interest.
- ?
- 4.7 LTS policy draft
- How long will the LTS be maintained? When do we stop supporting it?
- Gradle build tooling:
- Gradle is newer and more flexible than maven
- Are we open to migrating to Gradle?
- We haven't used it, but sounds promising
- We could convert project by project rather than needing to perform a massive waterfall event.
- We should confirm that the Gradle will work seamlessly with maven central.
- Bethany Seeger has worked with Gradle and likes it. Jared Whiklo prefers Gradle but not sure about the implications
- Does gradle do everything that our current maven plugins do?
- Can we add in a gradle file in parallel for a time?
- Aaron Birkland : To what extent would we need to reorganize the code to make Gradle work?
- Question of whether the site plugin will work in Gradle.
- If we move, everyone who uses fedora must learn gradle. To Bethany's point though, Gradle is very easy to use.
- If someone is willing to put in the work, general consensus that we would be open to being impressed.
- Christopher Johnson :
- gradle is more flexible for complex builds
- To Christopher Johnson : what problems are you seeing with the maven build with java 9?
- more options on the compiler need to be added - many more things need to be declared
- this will need to be done in Gradle
- in gradle you can write your own build specific plugin withouth having to version and deploy it independently
- Gradle is Groovy based.
- builds are failing on java9
- maven javadoc tool doesn't seem to work jdk9
- It took a bit of work to get fcrepo-java-client on jdk9
- more options on the compiler need to be added - many more things need to be declared
- Maven or Gradle, we'll still need to do some work to get the builds going on java 9
