Overview

The BodhiTree SDLC process: mandatory reading for every developer.

Document Purpose:
To standardize how developers contribute features using robust, test-driven development and best practices as part of Bodhitree’s SDLC improvement effort.

Each step below links to the page that covers it in detail.


📋 Step-by-Step Process for Feature Development

✅ 1. Submit Feature Request

Full procedure: Feature Request Process.

Reviewed by: KC, Varsha, Nagesh, Tejas, and a User Representative
Review happens during regular meetings.


🧱 2. Approval & Preparation

  • On approval:

    • Core Dev Team provides:

      • Best practices documentation

      • Access to repositories

How to ask for repository access: Access Request.


🧪 3. Developer Tasks

After getting access:

a. Planning

b. Coding

c. Testing

  • Run automated unit tests

  • Run manual unit tests

  • Ensure all test cases pass

Which tests to write: Testing Types in Bodhitree. How the test cycle runs: Testing Process.

d. Submission


🔄 4. Core Team Review & Integration

  • Teson Core Team will:

    • Merge code

    • Resolve any conflicts

    • Run automated integration tests locally


🚀 5. Deployment & Final Testing

  • Staging Server Deployment using Jenkins

  • Run:

    • Automated system tests

    • Manual tests for critical workflows


🌐 6. Production Release

  • Only after staging tests are successful

  • Production deployment is done and verified

Release naming and numbering: Versioning Convention and Current & Past Versions.


Found a bug instead?

Bugs do not go through the feature request flow. Follow Bug Reporting and file the issue using the format for creating an issue on GitHub.