1. Home
  2. Docs
  3. weDevs Engineering Proces...
  4. Feature Release Process for Dokan Cloud

Feature Release Process for Dokan Cloud

Purpose

To outline a clear and systematic approach for releasing new features from development to production, ensuring quality, compliance, and effective user adoption.

Scope

This procedure applies to all new features developed for the Dokan Cloud product. It involves the Development, QA, Content, Marketing, Design and Support teams.

Responsibilities

  • Development Team: Completes feature development and deploys to staging server; creates feature demo video.
  • QA Team: Tests the new feature on the staging server.
  • Content Team: Develops feature documentation and changelog.
  • Marketing Team: Plans and prepares promotional materials such as blog posts and email campaigns.
  • Support Team: Gains familiarity with the feature to assist customers effectively.
  • Design Team: Creates marketing materials for email, social media, and blog posts.

Procedure

  1. Feature Development Completion [Responsibility: Development + QA Team]
  • The development team completes the feature, and the QA team conducts initial local testing.
  • Once initial testing is satisfactory, the feature is deployed to the staging server at https://app.staging.dokandev.com/
  1. Quality Assurance Testing [Responsibility: QA Team]
  • Based on the Source of Truth (the original requirements from the PM team), the QA team conducts thorough testing with predefined test cases.
  • Any bugs or issues identified are reported back to the development team for resolution.
  • This process repeats until the feature meets all quality standards.
  1. Content Creation [Responsibility: Content Team]
  • Based on the Source of Truth (the original requirements from the PM team), the Content team prepares comprehensive documentation for the feature, which includes user guides, FAQs, and troubleshooting tips.
  • A changelog entry for the feature is drafted detailing the updates and improvements for https://dokan.co/cloud/changelog/ 
  • A featured image should be created by the design team for the changelog entry.
  1. Marketing Preparation [Responsibility: Marketing Team]
  • The Marketing team designs and schedules promotional activities, such as blog posts, social media updates, and email campaigns.
  • Materials are prepared to highlight the feature’s benefits and instructions for use.
  1. Support Team Training [Responsibility: Support Team]
  • The Support team reviews the feature based on the Source of Truth (the original requirements from the PM team) to understand the feature thoroughly.
  • Any necessary training sessions are conducted to ensure readiness to assist customers.
  1. Final Approval and Merge to Production [Responsibility: Development Team]
  • Once all teams have signed off on the readiness of the feature (QA confirms stability, Content confirms documentation completion, Marketing has promotional strategy ready, Support is trained), the feature is approved for production.
  • The Development team merges the feature into the production environment.
  1. Post-Release Monitoring [Responsibility: Development Team]
  • After deployment, the feature’s performance is monitored for any unforeseen issues.
  • Feedback from users is collected and analyzed to guide future updates or enhancements.

Documentation and Records

  1. Documentation is published at https://dokan.co/cloud/docs/.
  2. Issues and bug reports are logged at our GitHub repository: https://github.com/getdokan/project/  
  3. Customer feedback are recorded at https://feedback.dokan.co
  4. A release log is maintained to track the history and status of each feature release on our changelog portal: https://dokan.co/cloud/changelog/

Improvements and Recommendations

  1. Incorporate a feedback loop from end-users post-release to gather insights and improve future feature releases.
  2. Consider setting up automated testing tools on the staging server to speed up the QA process.
  3. Schedule regular inter-departmental meetings post-release to discuss what went well and what could be improved in the process.

Revision History:

  • Created on Apr 17, 2024 by Tareq Hasan
  • Updated on Dec 11, 2024 by Mohaiminul Islam
  • Updated on Dec 23, 2024 by Tanmay Das
  • Updated on Dec 24, 2024 by Mohaiminul Islam