You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
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)
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
- IRC:
Attendees
Agenda
4.3.0 Release is out
- Process reflections and improvements
- Release candidates?
- 4.4.0 focus
- Move projects into fcrepo-exts (see: F4 GitHub Organizations)
- Decouple those projects from the fcrepo4 pom.xml parent
- Plan on all extras projects starting independent versioning with 4.4.0
- Therefore, 4.4.0 will represent a common ground zero
- OSGi - demonstrate runtime configurability of F4?
...
Current Priorities
- Performance
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Single subject
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- fcr:metadata as a container
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Point-like objects
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Camel RDF serializer
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Migration-utils
- Bugs
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 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