...
The Template will includes these prompts. The Submitter should provides answers to and documentation for the following criteria:. The answers to these questions can be done in collaboration with the appropriate Special Interest Group and can reference any presentations done in a Special Interest Group meeting.
Functionality Name
Functionality Description
Desired release date
Expected TC review period
Describe how this functionality is unique
Describe how this functionality impacts or compliments existing functionality
Describe how this functionality fits into the roadmap
High level description of how the functionality is being built (back and front end aspects, interactions with existing functionality, etc.)
Describe any dependencies
Describe your user acceptance test plans
Links to documentation (technical and users) or describe documentation plans
Link(s) to presentation materials
...
Resubmission, Blocked, Deferred, or Cancelled Status
The Product Council plays a role in the decisions about what is included in the “Flower release” of FOLIO. This role doesn’t dictate what can or cannot be developed. This roles also doesn’t dictate what can or cannot be included in a FOLIO release supported by any particular service provider.
If none of the criteria are met even after the presentation, the Product Council will work with the Submitter to understand what is needed to continue the endorsement process. The ticket should be updated with decisions and any information relative to the successful endorsement of the new functionality.
The Submitter can also elect to cancel the submission.
The comments section of the JIRA may be used for this purpose.
If a meeting is required or desired, it's the responsibility of the Point of Contact to find a time that works and set the meeting up with the Product Council.
If the Submitter can elect to resubmit, then all issues are resolved and the Submitter requests a re-review.
JIRA workflow: the ticket is transitioned from REVIEW to SUBMITTED.
The Submitted can also elect to withdraw their submission.
JIRA workflow: the ticket is transitioned from REVIEW to CANCELLED.
The Submitted can also elect to defer their submission.
JIRA workflow: the ticket is transitioned from REVIEW to DEFERRED.
The Submitted and Product Council see that the new functionality is blocked.
JIRA workflow: the ticket is transitioned from REVIEW to BLOCKED.
Timeline: JIRA issues needs to pass to the next step within two weeks after submission. If that deadline falls on a holiday or weekend, then the week deadline is the next business day.
...