Page History

...

1. Fedora 4.7.1 release status
2. Stakeholders for release testing
   1. Widespread community release testing is important. To support this goal, I (David Wilcox) recommend we include a section on the release testing page that lists stakeholders using their confluence usernames, along with their institutions. These stakeholders would be representatives of institutions that are committed to testing release candidates as they become available. This would have the benefit of sending out direct notifications when a release candidate is ready for testing, and help ensure each release is tested by as many people/institutions as possible. 
3. Community planning
   
   1. Pain points
      1. Performance of "many members"
      2. Ugliness of pairtree resources
      3. ...
   2. Features of interest
      1. RDF1.1 serialization - breaking change
      2. AppleTrees - only for new installations
      3. Alignment with API spec - breaking change
      4. Bug fixes
   3. Mapping features to releases
      1. 4.7.x and 4.8.x
   4. Trajectory of development
      1. Community/ModeShape impl addresses bugs, aligns with API spec
      2. Alt-impls emerging in alignment with API spec
         • Derby
         • Cavendish
         • Trellis
      3. Common API and import/export facilitates transfer between impls
         • Transfer impact mitigated by "external-content"?
4. ...

5. Status of "in-flight" tickets

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...