[tor-bugs] #16570 [Internal Services/Service - trac]: Add new 'awaiting backport' state for Trac tickets?

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Mar 11 22:11:09 UTC 2019


#16570: Add new 'awaiting backport' state for Trac tickets?
----------------------------------------------+------------------------
 Reporter:  arma                              |          Owner:  (none)
     Type:  enhancement                       |         Status:  new
 Priority:  Medium                            |      Milestone:
Component:  Internal Services/Service - trac  |        Version:
 Severity:  Normal                            |     Resolution:
 Keywords:                                    |  Actual Points:
Parent ID:                                    |         Points:
 Reviewer:                                    |        Sponsor:
----------------------------------------------+------------------------

Comment (by teor):

 Replying to [comment:5 arma]:
 > adding teor to the cc list since I believe they are considering how best
 to describe and track tickets that are awaiting backports.

 Here's how the process works right now:
 1. we mark tickets that might need a backport with tags like
 "035-backport"
 2. when the ticket is merge_ready, it gets merged into the alpha and
 master branches
 3. the ticket is kept in merge_ready, but moved to the latest backport
 release milestone. (Which is currently 0.3.5)
 4. when a ticket gets backported to a particular release, it is moved to
 the milestone for the latest remaining release
 5. once a ticket has been backported to all releases, it is closed as
 fixed

 Here are the exceptional cases:

 When we stop supporting a release:
 A. we mark all tickets with a tag like "033-backport-unreached" (or "035
 -unreached-backport")
 B. we move tickets that can be backported to an earlier release into the
 relevant milestone
 C. we close tickets that can't be backported any further

 If we decide not to backport a ticket to any of the possible remaining
 releases:
 A. we remove the backport tags for the remaining releases
 B. I have been replacing it with a tag like "035-backport-unreached", but
 maybe that's confusing. I think we should use "035-no-backport"

 I quite like this process and I feel no need to change it.

 It's also relatively easy to write a ticket query that shows all
 backportable tickets:
 https://trac.torproject.org/projects/tor/wiki/user/teor#Backports:0.5daysperweek

 What I would like is a way to say "wait until after this ticket has been
 tested in the next alpha before backporting it".
 I'm using tags like "consider-backport-after-0404-alpha" right now, but
 I'd really like to be able to hide new backports until they have been
 tested enough.

 Here's are some filters we could use to hide tickets:
 * a particular release (when we add a particular version to the versions
 list in trac)
   * I don't know if Trac's query syntax supports filtering by the set of
 values in another field
 * a particular date (or a particular number of days in the future)
   * we'd need a new time field "backport", the query syntax would be
 "backport=..now"

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16570#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list