...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 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
Minutes
Release Update
4.6.1 patch release. Team: Jared, Dane Bernstein, Andrew Woods.
...
- Upgrade to ModeShape patch release (backup/restore capabilities compatible with newer version).
- Concurrent client creating same resource
Release should be out at the end of next week.
Kevin Ford : has not tested yet the concurrency issue yet. Hope Hopes to do it today. Limited test with 4.7 revealed no issues.
Andrew discusses the background of the issue: Modeshape 4 Infinispan into a non-Infinispan Modeshape ModeShape created the issue. Modeshape ModeShape applied patch to 5.2. and that patch has been back ported now, so that’s we have in 4.6.1. 4.7.0 is using the version of Modeshape ModeShape that’s in between, so that’s the reason for an issue. The solution suggested (by Kevin) is to continue with the releases (assuming no issues): follow up 4.7.0 with 4.7.1.
Aaron’s comment: all All commits will be fine with 4.7.1. release; other than bugs fixed, nothing much has changed.
...
- Please test stuff if interested in either.
- Add test pages to wiki.
- 4.6.1 sanity test for Hydra and Islandora needed. (Esme has volunteered).
Spec Issues
Adam Soroka (ajs6f) clarifies the background: “Trying to do a stable draft .. to present the community” with options (not finalize anything).
...
- Create-on-put: no negative response yet(only discussion with ben)
- Atomic operations: currently transactions have a URI. This is “better in some ways, not so in other ways.” ajs6f and Aaron Coburn seem inclined towards using headers.
...
ajs6f suggests different ways for the interested parties to submit feedback. Also stresses on the importance of finding out where the code base diverges from the spec.
Andrew’s comment/point # 1: Resources within a transaction are different resources than those outside. (That’s represented by a different URL.)
...
ajs6f: Perhaps a visual indication could be done to indicate transaction. A toggle perhaps.
Ben Armintor: Nothing should be changed until design documentation is done!
...
ajs6f: In conclusion, no one spoke up in favor of URI approach; there’s some interest in headers.
Andrew appreciates Adam’s effort.
Import/Export Sprint
- Nick: 3rd sprint, starting Monday. Short on volunteers (Tasks: (a) coding and (b) testing/documentation).
- Esme and Jared (and Danny Bernstein) are available.
- Bethany and Joshua are working on a Python tool to do verification
- Contact Bethany if interested in working on details.
- Looking for more volunteers.
Discovery Requirements
(barmintor mostly inaudible) -
- awoods (providing a summary): The issue was raised at HydraConnect higher; folks are still talking about it.
...
- "Discovery is not the right word here."
...
- Ben: No one word yet . . .
...
- Esme: “. . . not sure if there’s a good term to encapsulate that..”
...
- awoods: As the requirements do solidify, it would help to have them have mentioned in this call.
...
- ajs6f (side comment): Not sure if we are all (mikeAtUVa, e.g.) talking about the same thing.
...
Tickets
Please review tickets if you are the assignee.