| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
1110/2224/20222024
|
This document
includes information describing howdescribes Open-Source Community members
participateparticipation in SPARCRequest release process.
SPARC release schedules:
| R1 | R2 | R3* | R4 | ||
|---|---|---|---|---|---|
| SPARC-Request | X | X | |||
| SPARC-Dashboard** | X | X | |||
| SPARC-Report** | |||||
| SPARC-Forms** | |||||
| SPARC-Admin** | |||||
| SPARC-Fulfillment | X | ||||
| SPARC-Catalog | X |
*Research Master ID (RMID) release
**generally included in SPARC-Request releases
DOCUMENTATION PROCESS
Pivotal Tracker is the project-planning tool used to track development work for each managed product. Deliverables are in the form of stories (virtual cards) that move through a workflow of different states. Priorities are established and transparent so team members know what needs to be done, what is being doneworked on, and when it will be is completed. See quick start & demo of Pivotal Tracker HERE.
OPEN-SOURCE BUSINESS PROCESS MODEL
.png?version=1&modificationDate=1669143401898&cacheVersion=1&api=v2&height=400)
PROCEDURES
RESPONSIBLE PARTY | ABBREVIATION* |
|---|---|
Project Ops Team | PO |
Project Development Team | PD |
Open-Source Community Member | OS |
*Responsible parties' abbreviations appear in parentheses preceding the tasks below
(OS) Add a Pivotal Tracker (PT) Icebox story in the SPARC-OS Development project to report SPARC work requests. Story types will primarily be feature or bug. See specifics below on PT entry requirements.
(PO) Define story requirements to move forward in the development cycle
(PO) Update story label to denote next steps or information for OS community, who performs the following actions, per labeled status:
- (OS) Todostories - begin considering the topic, which will move into another status to further define requirements
- (OS) For discussion - participate and respond to requests for additional information and discussion
- (OS) Operations agenda - participate in initial meeting discussions about the story that define requirements, if needed.
- (OS) For review - perform and document a review of the proposed feature or reported bugs, recording institutional priority as a task on the story (see example below)
Ratings: High: essential to business operations
Medium: fairly important to business operations
Low: little to no importance on business operations
- (OS) Operational committee approved - refer to this final OS committee action for story status
- (OS) Institutional Institutional name_contribution - contribute to the story development, following steps 7-10 below)
(PO) Include story in project Backlog section to prioritize for a release (iteration).
- (PO, PD) Determine stories that will go in next sprint cycle
- (PO) Assign story to release
- (OS) - refer to label for release assignment (e.g., version 3.9.0)
- (PD; OS) Update story state to Started, moving story into project Current Iteration section.
- (PD/PO; OS) Complete story development and testing, per following workflow.
- (OS) Participate in the development and testing process by:
- Responding to any requests for information or testing through comment entry in the story's Activity section.
- Entering in pull request when contributing development code. Include any rake tasks as comments in Activity section.
- Responding to any requests for information or testing through comment entry in the story's Activity section.
(PO) After story acceptance, added to release documentation list
(PD) Release deployed to production.
- (OS) Access release documentation for implementation planning
- (OS) Following 2-week release monitoring, expect to get communication of SPARC's availability for you to implement.