This roadmap assumes ~3 month, time-boxed, minor releases.  The roadmap considers larger-scale tasks only.  Each release will also include numerous bug fixes and minor improvements, as needed.

Note that S-RAMP 1.0 will be defined purely by 100% spec compliance.  Once compliance is met, 1.0.0.Final should probably be released.  With that exception, most releases are expected to be minor versions.

Release 1

• Develop a POJO event model, serializable into JSON [SRAMP-433] Create a proper Event producer for s-ramp - JBoss Issue Tracker
• Publish JMS topic and queue events for artifact additions, updates, and deletions [SRAMP-433] Create a proper Event producer for s-ramp - JBoss Issue Tracker
• Completion of the S-RAMP TCK (external project) [SRAMP-168] Create a TCK test suite - JBoss Issue Tracker
• Support Wildfly [SRAMP-517] Support Wildfly - JBoss Issue Tracker
• EAP/Tomcat integration tests (done)
• UI search improvements and query-syntax "training" [SRAMP-554] Improve the UI search capabilities and query syntax support - JBoss Issue Tracker
• UI query-syntax tab completion [SRAMP-468] tab completion for UI queries - JBoss Issue Tracker
• Finalize the Maven facade, include adequate testing, and deprecate the Maven Wagon
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Release 2

• Fine-grained, role-based access control [SRAMP-163] Authorization: Role based access to S-RAMP data - JBoss Issue Tracker

• Support for WADL files [SRAMP-404] Create a Deriver for WADL files - JBoss Issue Tracker

• Fuse integration tests [SRAMP-460] Integration tests: Fuse - JBoss Issue Tracker
• UI integration tests [SRAMP-472] Selenium UI tests - JBoss Issue Tracker
• Increased unit test coverage
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Release 3

• OpenShift cartridge [SRAMP-463] OpenShift cartridge - JBoss Issue Tracker
• Improved relationship resolution [SRAMP-465] Investigate alternative methods for relationship resolution - JBoss Issue Tracker, [SRAMP-466] Better utilize batch mode for relationship resolution - JBoss Issue Tracker, https://issues.jboss.org/browse/SRAMP-466[SRAMP-469] Make better use of SwitchYard SCA during relationship resolution - JBoss Issue Tracker
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Release 4

• Camel endpoint [SRAMP-556] Investigate creating a Camel endpoint plugin - JBoss Issue Tracker
• Artifact relationships visualization UI [SRAMP-467] UI: relationship visualizations - JBoss Issue Tracker
• Artifact auditing UI [SRAMP-313] Implement Audit History page - JBoss Issue Tracker
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Release 5

• User dashboard ("my activity stream", recently added artifacts, etc.) [SRAMP-312] Implement a User dashboard page - JBoss Issue Tracker
• Port shell commands to Fuse/Karaf/Felix [SRAMP-435] Investigate porting S-RAMP CLI to Felix commands - JBoss Issue Tracker
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Release 6

• Create an uber-war for out-of-the-box basic functionality on any app server [SRAMP-516] Consider an "uber war" with basic functionality for any app server - JBoss Issue Tracker
• S-RAMP spec conformance (ongoing) [SRAMP-462] S-RAMP 1.0 spec compliance and TCK - JBoss Issue Tracker

Unknown

• Shell improvements based on newer aesh capabilities [SRAMP-396] S-RAMP Shell improvements and new capabilities - JBoss Issue Tracker
  Desirable, but the aesh version utilized must align with the rest of Fuse/FSW.
• UI: Develop "workbench components", align with PatternFly, support UberFire, etc.
  The requirements and approach are still under discussion
• Docker image [SRAMP-464] Docker image - JBoss Issue Tracker
  Unknown if actually needed