[tor-bugs] #12586 [Ooni]: Specify versioning scheme in Ooni Release-Procedure.md

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

#12586: Specify versioning scheme in Ooni Release-Procedure.md
------------------------------------------+-------------------------
 Reporter:  nathan-at-least               |          Owner:  hellais
     Type:  defect                        |         Status:  new
 Priority:  normal                        |      Milestone:
Component:  Ooni                          |        Version:
 Keywords:  versioning release packaging  |  Actual Points:
Parent ID:                                |         Points:
------------------------------------------+-------------------------
 The current release procedure for Ooni would benefit from describing the
 versioning scheme.  This should serve two purposes:

 * users can make decisions about installation and upgrade.  For example,
 they may choose to *not install* a new release if they prefer to only
 upgrade to security fixes or "stable" releases.
 * if a new Ooni dev comes along and makes a new release, they will not
 violate the expectations of users.

 Keep in mind there are at least two categories of "user": probe operators
 and backend service providers.

 As a bonus, the versioning scheme should also be described in each
 package's own documentation, or perhaps those docs should link to a single
 source of truth in the spec repository.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12586>
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