Logo
  • 1. Style and Idiomatic Code
  • 2. Programming Best Practices
  • 3. Product Development
    • 3.1. Tickets
    • 3.2. Documentation
    • 3.3. Release process
    • 3.4. Sales and Marketing
    • 3.5. Support
  • 4. Running the Virtual Office
  • 5. Library
  • 6. References
C.G.E.C.K.
  • »
  • 3. Product Development
  • Edit on GitHub

3. Product Development

These pages describe the way we handle / manage and develop the product produced by the Chevah project.

They might not fit other projects with other requirements.

  • 3.1. Tickets
    • 3.1.1. General
    • 3.1.2. Work priority
    • 3.1.3. Support tickets
    • 3.1.4. Bug / Defect reporting
    • 3.1.5. Ticket details
    • 3.1.6. Milestone planning
  • 3.2. Documentation
    • 3.2.1. Introduction
    • 3.2.2. Narrative documentation
    • 3.2.3. Structure of the Documentation
    • 3.2.4. Using reStructuredText (rst)
    • 3.2.5. Updating the documentation
    • 3.2.6. Marketing / Promotional Materials
    • 3.2.7. Known Issues
    • 3.2.8. Mock ups and designs for the website
  • 3.3. Release process
    • 3.3.1. General
    • 3.3.2. Release Planning
    • 3.3.3. Release Review Process
    • 3.3.4. Release Manager
    • 3.3.5. The Release Branch
    • 3.3.6. Release Notes
    • 3.3.7. Version Management
    • 3.3.8. Compatibility Policy
    • 3.3.9. Releasing a forked library
    • 3.3.10. Releasing a library
    • 3.3.11. Releasing a product
  • 3.4. Sales and Marketing
    • 3.4.1. Introduction
    • 3.4.2. Product Demo
    • 3.4.3. Marketing / Promotional Materials
  • 3.5. Support
    • 3.5.1. Introduction
    • 3.5.2. Chat
    • 3.5.3. Licenses and support contract
    • 3.5.4. Support Case Management
Previous Next

© Copyright 2022, Chevah Team. Revision 483ab991.

Built with Sphinx using a theme provided by Read the Docs.
Read the Docs v: main
Versions
latest
main
Downloads
On Read the Docs
Project Home
Builds