Release Process
Customer Issue/Feature Requests
As customers utilize the ticketing system to submit their issues or new feature requests, these items are added to the backlog.
Issues:
Once reported issues are identified, they undergo testing in our QA environment to confirm reproducibility and facilitate debugging.
If the issue is a product defect, such as an error or incorrect math, and it can be replicated in QA, it will be addressed and resolved within an 8-week timeframe.
Note
It is important to note that the 8-week timeframe starts once we can successfully replicate it in our QA environment.
Feature Requests:
Feature requests entered in the product backlog will undergo review and prioritization.
Note
It is important to note that we aim to fulfill 40% of customer feature requests annually.
Prioritization Process
Prioritize high-priority items first, such as critical bug fixes affecting core functionality.
Review the product roadmap to identify focus areas for the upcoming release.
Review the backlog user stories, including new features and customer requests, prioritize them based on the determined focus areas, and add them into sprints.
Week 1: Start Release Cycle
Sprint Cycle:
Development Starts.
OnePlan sprints have a duration of 2 weeks.
QA Testing:
New code is developed and pushed to our QA environment twice a day.
Testing is ongoing throughout the entire life cycle of development.
The QA team will review the backlog and identify items tagged as “Ready for QA”.
Any issues found during testing are sent back to the development team for correction.
Once the QA team has completed their test cases against the acceptance criteria, the item is deemed “Ready for Regression Testing”.
Regression Testing:
Code is pushed to our Staging environment for regression testing.
Previously executed test cases are rerun to ensure that existing functionalities still work as expected after code changes or updates.
Verifying that the software's core functionalities continue to operate correctly after modifications.
Week 4: Minor Patch Released to Production
This will contain bug fixes and any defects found.
Regression testing will occur after the patch is released.
Week 6: Code Freeze
At this point no new code changes, enhancements, or features are allowed to be implemented or introduced into the software system.
During the code freeze, developers may focus on resolving critical defects and performing system optimizations.
This marks the point at which customers and partners can log in and create a site to test new functionality.
Additionally, customers can deploy their production custom code to the stage environment and perform regression testing.
Note
It is important to note that our QA team does not test customers' customizations.
Week 6: Release Notes
The release notes will be published on our support site at https://support.ppmworks.com.
This provides a 4-week window to prepare for the production release.
Week 8: Pre-Release Webinar
Between weeks 6 and 7, you will receive an invitation to a webinar scheduled for week 8.
This webinar will cover the new features and functionality included in the upcoming release.
Week 10: Production Release
New functionality release will be pushed out to production. This includes the following environments:
- my.oneplan.ai
- eu.oneplan.ai
- au.oneplan.ai
- us.oneplan.ai
- ca.oneplan.ai
Regression testing will occur after the production release.
OnePlan operates within a SaaS environment, software releases are mandatory for all users since updates are automatically applied to the entire user base.
Note
It is important to note that certain features will be offered on an opt-in basis, and these will be listed in the release notes.
Releases will generally occur on Fridays.
Releases on US holidays will be adjusted accordingly.
Releases will roll out when ready, ensuring that the release is deployed only when it is fully tested and prepared.
Comments
0 comments
Please sign in to leave a comment.