[tor-bugs] #12587 [Ooni]: Specify Ooni "next release" process.

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#12587: Specify Ooni "next release" process.
-------------------------------+-------------------------
 Reporter:  nathan-at-least    |          Owner:  hellais
     Type:  defect             |         Status:  new
 Priority:  normal             |      Milestone:
Component:  Ooni               |        Version:
 Keywords:  release packaging  |  Actual Points:
Parent ID:                     |         Points:
-------------------------------+-------------------------
 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.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12587>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs