Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Boards
    Boards
  • Wiki
    Wiki

Content

You are here:
  1. Wiki
  2. Release Process

Release Process

  • More
    • Print
    • Table of contents

  1. When to start - entry criteria?

    1. When is the next release?

    2. Stable process for Nextcloud version bumps

  2. Release preparation

    1. What steps are taken, who is doing what?

    2. Timelines and Timeframes

  3. QA process

    1. How is giving the green light?

    2. How is doing and communicating with whom?

  4. Release - exit criteria

    1. When is the final release?

    2. Have a checklist to know what conditions need to be met.

  5. After release

    1. Handing over process

    2. Communication, who to ping


  1. When to start a release - entry criteria?

    1. External reasons

      1. Nextcloud Major version release

        1. Have it released between 4 to 2 weeks before Nextcloud release

        2. Have version bump released with other Bugs or Features id possible

        3. If not a NC version bump in the release is a patch release

      2. Dependencies change or break

        1. Release only if really needed, but as soon as possible

      3. Security issues

        1. Do not create a work package in the a public accessible project

        2. Release as soon as possible

    2. Internal reasons

      1. Features is finished

        1. No hard rules and based on strategy.

        2. Normally features/epics should be released within 2 weeks.

      2. Bugs are fixed

        1. Soonish, if Bugs are merged they should be released within 4 weeks

  2. Release preparation

    1. What steps are taken, who is doing what?

      • Version should have been already created in OpenProject before, if not create one (Dominic)

      • Query should have been already created in OpenProject in the Nextcloud project beforehand and mark it as favorite, if not create one (Dominic)

      • Mage sure all work package are assigned to the version (Dominic)

      • Announce planned release to team (Product owner - Dominic)

      • Create work package for release. (Or template project for release) (Dominic)

      • Create branch if needed in GitHub (Sajan)

      • Change deployment target if needed on QA deployment script (DevOps)

      • Add change logs (Sajan)

      • Tag version in Github (Sajan)

      • Ping QA (Cécile) that release is ready for testing (Sajan)

    2. Timelines and Timeframes

      1. Needs to be defined

  3. QA process

    1. How is giving the green light?

      1. Project owner - Dominic

    2. How is doing and communicating with whom?

      1. By default between Sajan and Dominic

  4. Release - exit criteria

    1. When is the final release?

      1. Have checklist that needs to be defined like in OpenProject template release project

  5. After release

    1. Handing over process
Loading...