-
Notifications
You must be signed in to change notification settings - Fork 66
Project Management
This page describes how Jiva project is maintained. Jiva Project includes - both data engine, the code maintained in https://github.com/openebs/jiva, as well as the control plane components like provisioners and metrics collectors available in https://github.com/openebs/maya, https://github.com/openebs/external-storage, https://github.com/openebs/jiva-csi
Jiva follows OpenEBS Project Management guidelines and is tacked using GitHub as follows:
- GitHub Milestones provide a snapshot of short term goals
- GitHub Projects are used to track the midterm goals
- GitHub Issues are used to capture long term goals. The issues that are neither part of the milestones or projects are tagged with a label "Backlog"
Specifically for Jiva:
-
GitHub Issues (usually created under the https://github.com/openebs/openebs/issues repo) are used to track features/bugs. In some cases, users end up creating issues directly under the https://github.com/openebs/jiva/issues or other dependent repos. There will be a corresponding tracking issue created under https://github.com/openebs/openebs/issues by the project maintainers. Every new GitHub issue will be either part of the milestone or project and tagged as Future Backlog in the Bug Triage meeting.
-
GitHub Milestones will be used to track the release items. Jiva releases will be aligned with the OpenEBS releases. A monthly release cadence is maintained. Minor releases that fix some user-reported issues can be made on-demand from the specific release branch. https://github.com/openebs/openebs/milestones are used to track planned items for a given OpenEBS monthly release. https://github.com/openebs/jiva/milestones milestones will be used to track the PRs targeted for the corresponding Jiva release.
-
GitHub Project Tracker will be used to for getting a snapshot of items planned for the immediate Major release. For Jiva v2.0, the tracker is at https://github.com/orgs/openebs/projects/1
- Daily OpenEBS Standups are used to track the readiness towards the planned release items. This sheet will be used to track the estimated due dates towards the release goals like RC builds. The sheet also will be used to track some release checklist items. OpenEBS Planning Sheet
- Weekly Bug Triage Meeting by the Jiva maintainers to check on the new issues created in the past week and help the assign the issue with labels and/or include them into project/milestones. Check the sanity of projects and milestones. Though planned for weekly, the maintainers can do this as the issues come in to be more responsive.
- Bi-weekly OpenEBS meeting to help with product backlog prioritization by taking end-user and feedback from other dependent teams.
This is a list of items that need to be further investigated before creating an issue. These are examples of items that came up during discussions with users and other collaborators.
- Support for Direct Backup/Restore to S3