...
Discuss: Java8 Stream construct vs. Guava Iterators for lazy evaluation (the kernel modules currently rely extensively on Iterators, for example: RdfStream)
- 4-position versioning scheme, redux
- Github Housekeeping: Close stale branches, old issues
- 2015-08-14 - Fedora API Extensions Meeting tomorrow
...
Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
- We have been using Guava, but now Java8 provides us with a lot of the same functionality without external libraries. So, should we refactrefactor?
- Pros: Less code. Less external library dependencies.
- Cons: Stream and iterator are not the same thing.
Not a full find and replace.
Consensus: Use stream where it is appropriate. Use iterator where it is appropriate.
- Meta-discussion about priorities and focus
Jira server DuraSpace JIRA jqlQuery filter=13121 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Action: Andrew Woods to restructure priorities and focuses in JIRA to represent the project vision [as Andrew Woods described it earlier in this call].
- Discussion about Fedora's versioning schemascheme
- Should we move to normal sematic versioning?
- Should we have LTS releases, or terms of support for each release?
- If we abandon the 'Product version' in our versioning policy, how do we handle messaging and marketing – communication?
- No general consensus on moving from status quo.
- We should do some house keeping!
- Keep an eye on GitHub notifications to see if you have pinged.
- Please attend the meeting if you can.