Skip to content

Release Team

Quick Answer

The Release team at Mujin manages the lifecycle of our software releases, packaging complex codebases, coordinating updates across branches, and validating deployment configurations for safe updates.


We control the gate to stable production software:

Packaging & Build Control

We package software components into stable, versioned installer units (like Debian packages) with managed dependency structures.

Branch & Tag Management

We organize git branching strategies, create release tags, and coordinate code freezes before major updates.

OTA Package Integrity

We verify the security, checksums, and rollback scripts of over-the-air update packages before deploying them.


What technology stack and engineering workflows do we use?

Section titled “What technology stack and engineering workflows do we use?”

We follow strict versioning rules and continuous deployment checks:

  1. Branching & Packaging Tools
    • Git for source code branch and release management.
    • Debian packaging format (dpkg, apt) and custom packaging scripts.
  2. Build Distribution
    • Package repositories and file servers for caching and distribution.
    • Using automation tools to compile changelogs and release notes automatically.
  3. Rollback & Verification Workflow
    • Testing release updates on virtual machine clones to identify installation bugs.
    • Validating clean fallback behaviors if target controllers lose power during updates.

We look for highly structured and careful release coordinators:

  • Technical Competence: Strong experience in build tools, git, Linux environment setup, and script automation.
  • Effective Collaboration: Coordination with QA and development leads to verify feature readiness and sign off releases.
  • Continuous Learning: Finding ways to speed up packaging compilation and automate changelog tracking.

If you want to manage release cycles for intelligent robotic fleets, apply today: