Kleros Moderate
  • Introduction to Kleros
  • Kleros FAQ
  • Governance
  • PNK Token
  • They talk about Kleros
  • Products
    • Court
      • Kleros Juror Tutorial
      • Famous Kleros Cases
      • What happens during a dispute?
      • Kleros & Credible Neutrality
    • Proof of Humanity
      • Proof of Humanity Tutorial (Register & Vouch)
      • Proof Humanity Tutorial (Remove & Challenge)
      • Proof of Humanity FAQ
    • Tokens
      • Kleros Tokens Tutorial
    • Curate
      • Kleros Curate Tutorial
    • Oracle
    • Governor
    • Escrow
      • Kleros Escrow Tutorial
      • Kleros Escrow Specifications
    • Linguo
      • Kleros Linguo Tutorial
      • Step-by-step Tutorial
        • Requesting translations
        • Working as a translator
        • Reviewing translations
      • F.A.Q
      • High-level Overview
    • Moderate
      • Susie
        • Getting Started
          • Add Susie
          • Start Susie
        • Basics
          • Welcome
          • Language
          • Notifications
        • Rules
        • Reports
        • Evidence
        • Federations
  • INTEGRATIONS
    • Overview
    • Types of Integrations
      • 1. Dispute resolution integration plan
        • Smart contract integration with Kleros Court (Arbitrator)
        • Use Cases
          • DeFi Insurance
          • Gaming
        • Channel partners
          • How to use Reality.eth + Kleros as an oracle
          • Safe Zodiac integration
        • Integration Tools
          • Escrow React
          • Escrow SDK
          • Centralized Arbitrator
      • 2. Curated-data integration plan
        • Interact with Arbitrable apps built on top of Kleros Court
    • Policy writing guide
    • Live & Upcoming Integrations
    • Kleros Analytics
    • Scalability & Cross-chain
      • Using Kleros arbitration for Dapps on xDai/Gnosis
    • Integrations FAQ
  • Developers
    • Arbitration Development
      • ERC-792: Arbitration Standard
      • ERC 1497: Evidence Standard
    • Arbitration by Example
      • ArbitrableDeposit.sol
      • TwoPartyArbitrable.sol
      • Rental.sol
      • ArbitrableTransaction.sol
      • MultipleArbitrableTransaction.sol
      • MultipleArbitrableTokenTransaction.sol
    • Archon: Ethereum Arbitration Standard Interaction Library
    • Deployment Addresses
    • Curate Classic: Integration for Devs
    • Light Curate: Integration for Devs
    • Guide for Preparing Transactions
  • Contribution Guidelines
    • Overview
    • General Dev. Workflow
      • Task Tracking & Lifecycle
      • Releases
    • Smart Contract Workflow
      • Task Tracking & Lifecycle
      • RAB - Review, Audit, Bounty
      • RABd (+ Deploy)
      • Reporting Vulnerabilities
    • Code Style and Guidelines
      • Git
      • Solidity
      • Web Languages
    • License & Code of Conduct
      • License
      • Code of Conduct
  • Additional Resources
    • Discord
    • Telegram
    • Governance Forum
    • Twitter
    • Blog
    • Reddit
    • Github
    • Slack
Powered by GitBook
On this page
  • Branch Deploys
  • Version Bumps & Releasing
  1. Contribution Guidelines
  2. General Dev. Workflow

Releases

How we push new code to staging, production, and beyond.

PreviousTask Tracking & LifecycleNextSmart Contract Workflow

Last updated 2 years ago

Branch Deploys

In an effort to keep everything as automated as possible, we have two main protected branches that get automatically deployed in most of our projects:

develop

master

Deploys to a staging environment.

Deploys to a production environment.

Pull requests also get deploy previews when applicable.

Version Bumps & Releasing

When a task is finished, it gets merged to develop. When develop is tested and ready to become a production release, the following process takes place:

  1. We run on develop and take advantage of our style conventions to automatically create or update a changelog and bump the version number following guidelines.

  2. We push and submit a pull request to master.

  3. We conduct one final review before merging and letting CI/CD take care of the rest.

standard-version
Git
semver