Opened 5 years ago

Closed 15 months ago

#12587 closed defect (wontfix)

Specify Ooni "next release" process.

Reported by: nathan-at-least Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords: release, packaging, archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The current Ooni release document covers how to do a release. What about the "next release"? It would be nice to specify (or link to) a description of the process for preparing a next release. This should cover details like:

  • how to find the deadline, schedule, version number, for the next release.
  • how to find all tickets specific to the next release.
  • any details about "meta-criteria" or the process of release planning. Some examples:
    • "we have a monthly meeting to discuss the next release"
    • "we do a feature freeze, then release on a strict 3-month periodic schedule"
    • "after we make a release, we have a meeting and decide on all tickets which are targets for the next release, and we make releases whenever those tickets are closed."

It can also be useful to define a release process for emergency security fix releases, because it's especially nice to be prepared in that case. A good technique here is to assign a single person unambiguously as responsible for a security release to prevent people from blocking or stalling due to responsibility confusion.

Child Tickets

Change History (2)

comment:1 Changed 22 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 15 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.