You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
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
- IRC:
Attendees
Agenda
Updates from the last two weeks?
- Tickets aligned with roadmap themes
API Specification
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Service: CRUD
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Service: Versioning
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Service: Transactions
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Service: Fixity
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Service: Authorization
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
SPI Specification
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Runtime configurability
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Performance / Scale
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
FCREPO-1777 - Vagrant Integration Testing
Status of "in-flight" tickets
key |
summary |
type |
created |
updated |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
...
Ticket Summaries
Please squash a bug!
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Tickets resolved this week:
key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Tickets created this week:
key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Minutes
Updates from last two weeks
- Last week was in-flight tickets
- FCREPO-1777
- Methodologies around packaging (came up during work on FCREPO-1823)
- Outstanding pull requests on fcrepo4-client
- Messaging around getting folks to focus on the new fcrepo4-java-client as opposed to fcrepo4-client
- A ticket will be created to survey the landscape of LDP clients (Jared Whiklo will do it)
- Discussion around upgrading to Jena 3.0 (rdf 1.0 vs 1.1)
- Breaks about a dozen tests because of how literal behaviour changes
- Should we wait?
- January release
- empowering folks to cut releases for individual modules
- policy? consensus on a call?
- Tickets aligned with roadmap themes