This Roadmap is a reflection of the current plans of the COmanage Project, and is provided for informational purposes only. Specific release dates are not guaranteed.

Schedule

Beginning with Registry v4.0.0, the COmanage Project is planning on two Feature Releases per year, roughly aligned with the Internet2 Global Summit (usually around April) and Technology Exchange (usually around October). Feature Releases are those that end in .0 (eg: 3.3.0, 4.0.0), and can be either a MAJOR or MINOR release as per Semantic Versioning.

• The scope of each Feature Release ("Feature Freeze") will close approximately two months prior to the target release date. After Feature Freeze, commits may only be made for features already in scope and for bug fixes.
• The first Release Candidate ("Code Freeze") will occur approximately one month prior to the target release date, at which point only bug fixes may be committed. Additional Release Candidates will be prepared as needed, which may impact the actual release date.

Hot Fix Releases (PATCH releases as per Semantic Versioning) will continue to be released as needed.

The Project has not yet established a release schedule for products other than Registry.

Roadmap

The Roadmap is intended as a high level overview. Additional details are available in JIRA.

Product and Version	Target Release Date	Scope and Functionality
Registry v5.0.0	TBD	Framework Migration Backwards incompatible changes, TBD Instrumentation and Logging
Registry v4.9.9	TBD	Non-production transformational release in preparation for Framework Migration
Match v1.3.0	TBD
Registry 4.4.0	Release Candidate: 5 February 2024 Final Release: 4 March 2024
Match v1.2.0	Final Release: 3 October 2023	Attribute Invalidation Trust Mode for Systems of Record Better styling for read-only views
Registry v4.3.0	Release Candidate: 28 August 2023 Final Release: 3 October 2023	Petition Read API added to Core API Department Read/Write and Organization Read/Write APIs added to Core API Support for prebuilt multi-arch container images Approver Special Group Type Maximum Retry added for Queue Based Provisioning DuplicateCheckEnroller Plugin Configurable Email Templates for Petitions Pending Approval (Approver Notification) Password Dashboard Widget Group Member count on Group pages
Registry v4.2.0	Release Candidate: 17 April 2023 Final Release: 17 May 2023	Support for Upload of RFC 4716 SSH Public Key Configuration of Namespace Assigner Name Type Configurable Table Prefix for SqlProvisioner SqlProvisioner Support for eduPersonAffiliation Improvement of CO Person save for deployments with many COUs Container image/build enhancements Display Registry Version for Container Deployments CoreAPI max query limit increased Increase cm_kafka_servers.brokers column size
Match v1.1.0	Final Release: 18 January 2023	New features Track History of Matchgrid Callback on Potential Match Resolution Finish Migration to DBAL UI/UX Improvements
Registry v4.1.0	Release Candidates: 7 December 2022, 9 January 2023 Final Release: 17 January 2023	New features ApiSource Accepts Multiple Roles CoreAPI Improvements Elector Data Filter Enrollment Flow Integration with ID Match Identifier Assignment Plugins Manager Data Model Element Match Callback on Resolution Novi Organizational Identity Source OIS Data Filters Recovery Widget Sponsor Renewal Widget SqlSource Person Vetting Service Eligibility Plugin Container Refactoring
Match v1.0.0	Release Candidates: 17 November 2021, 1 January 2022, 25 April 2022 Final Release: 5 July 2022	Initial Release
Registry v4.0.0	Release Candidate: 13 September 2021 Final Release: 4 October 2021	New features Asynchronous (Queue Based) Provisioning Dictionaries Global Localizations Identity Documents MFA Enrollment Manager Nested Groups Boolean Logic Organization Object
Registry v3.3.0	Release Candidates: 7,20,29 July 2020 Final Release: 16 August 2020	New features Cluster Management, including Unix Clusters Nested Groups CO Group Attributes, including Identifier Assignment Data Filters Ad Hoc Attributes ID Match API Integration MidPoint Provisioning Plugin SQL Provisioning Plugin BulkLoad Shell
Registry v3.2.0	Release Candidate: 18 December 2018 Final Release: 6 January 2019	New features voPerson and LDAP Attribute Options Server Registry Objects Dashboards Salesforce Provisioning Plugin Crowd Provisioning Plugin Duplicate CO Group Membership Validity Dates Locally Stored Terms and Conditions
Registry v3.1.0	Release Candidates: 2,24 January 2018 Final Release: 14 February 2018	New features Searching Simplified Account Linking Processes via EnvSource Mailing List "Native Object" Support Credential Management, including Passwords and Certificates CO Departments URLs as Person Attributes MediaWikiProvisioner Salesforce Organizational Identity Source Improvements to Organizational Identity Sources Support for Additional SSH Key Types
Registry v3.0.0	Release Candidates: 7,30 August 2017 Final Release: 19 September 2017	Refreshed UI, improved mobile support and accessibility Early access to this version is available via the git develop branch, but this branch is not suitable for production deployments.
Registry v2.0.x	Final Release: 23 December 2017	Maintenance Releases
Registry v2.0.0	Release Candidates: 11,28 March 2017 Final Release: 13 April 2017	New features Organizational Identity Sources and Pipelines ORCID Integration LDAP Schema Plugins Services and Service Portal, and Service Tokens Population-Specific Provisioning Themes Email Message Templates Attribute Enumerations Identifier Validation Authentication Events
Registry v1.0.7	5 April 2017	Maintenance Release; Final release of the 1.x series

The previous roadmap is available here. 

Container Roadmap

The Packaging team maintains a Container Roadmap here.

COmanage Roadmap

Note that each version builds upon the previous versions and will allow for all listed applications.

Alpha (due Apr. 2009)

Expected user experience:
In the Alpha release COmanage can be (easily) configured to work with only one federation (InCommon, intra-campus, other). You will only be able to invite people to join your CO who are from sites that belong to that federation; those people will be able to use the domesticated applications within your CO instance. The installation process will be minimalistic - there will be a virtual machine image available as well as documentation on how to configure and manage a CO instance.  There will also be a demo installation in the EC2 or Internet2 space for people to explore without having to install their own COinstance.

Core Product

• Shibboleth SP (limited to one federation only)
• Grouper/LDAPPC
• OpenLDAP
• MySQL
• COllabmin interface

Domesticated Apps

• Sympa
• Drupal
• Confluence

Other features

• Debian Repository

Beau Jest (due Dec. 2009)

Expected user experience:
Functionality from a user perspective will be very similar to Alpha; much of the change will be seen by the COllabmin. There will be a better administrative interface for Shibboleth, and multi-federation support will be enabled. There will also be several new domesticated applications within the virtual appliance. The COllabmin interface will be heavily redesigned to include tabs for each application to standardize how people can administer the different apps.

The installation will become more advanced with an install script that will allow the prospective COllabmin to customize the COmanage instance to use infrastructure outside the COmanage environment.  A default virtual machine image and an online demo playground will remain available to users only interested in exploring COmanage.

Core Product expansion

• Shibboleth (complete)
• COllabmin redesign (tabs)
• Start of a broader installation script to allow more flexibility in identity infrastructure

Domesticated Apps

• Jira
• bedework
• Zimbra

Other features

• Focus on user interface
• Focus on installer script

Calliope - aka, COmanage 1.0 (due Apr. 2010)

Expected user experience:
The focus for this version of COmanage is on the visual  experience for the COllabmin. The interface will change to match the Fluid model <http://wiki.fluidproject.org/display/fluid/Fluid+Project+Wiki>.  Additional domesticated applications will be added to the service. This will be considered the first complete version of COmanage.

In an ideal world, more applications will be designed with domestication in mind - the COmanage team will not be required to focus on hooks, API, or any other interface magic to allow for the addition of new applications.  Each COmanage site will be able to pick and choose their own software and methods for collaboration without restriction.

Domesticated Apps

• phpBB (forum)
• IM (jabber)

Other features

• Fluid-ized interface
• RedHat/CentOS version

2.0 and beyond

...