Deploy sbws in the rest of bwauths
When deploying (after all tickets are resolved) sbws in all the remaining bwauths (3/6)
-
send an email to the dirauths to start the transition process. -
deploy every new change in only one bwauth, wait 5 days or a week, then test the next. -
send mail to next bwauth to have sbws deployed -
longclaw (deployed but found some issues: #40087 (closed), #40106 (closed), #40107 (closed)) -
maatuska (deployed but found some issues: #40088 (closed) , #40086 (closed), #40087 (closed), #40092 (closed)) -
bastet (deployed but found an issue: #40091 (closed)) -
faravahar (deployed but found some issues: #40105 (closed), #40111 (closed)) -
gabelmoo (deployed but found some issues: #40108 (closed), #40109 (closed), #40110 (closed), #40115 (closed), #40116 (closed) though none of them seems critical; #40112 (closed), #40119 (closed), #40121 (closed)) -
moria
-
Currently, these are the new changes we should test:
-
!9 (merged) -
!14 (merged) -
!15 (closed) -
!16 (merged) -
!18 (merged) -
#29710 (closed) -
#33198 (closed) -
#33947 (closed) -
#40008 (closed) -
#40038 (closed) -
#40041 (closed) -
#40043 (closed) -
#40044 (closed) -
#40048 (closed) -
#40049 (closed) -
#40051 (closed) -
#40059 (closed) -
#40060 (closed) -
#40064 (closed) -
#40086 (closed) -
#40087 (closed) -
#40088 (closed) -
#40091 (closed) -
#40092 (closed) -
#40105 (closed) -
#40106 (closed) -
#40107 (closed) -
#40108 (closed) -
#40109 (closed) -
#40110 (closed) -
#40111 (closed) -
#40112 (closed) -
#40115 (closed) -
#40116 (closed) -
#40119 (closed) -
#40121 (closed)
Note that this was a parent ticket for many others mentioned by @tracbot at #33121 (comment 2518949), very similar to the https://gitlab.torproject.org/tpo/network-health/sbws/-/issues?label_name%5B%5D=sbws-roadmap tickets and %sbws: 1.1.x-final milestone
Edited by Georg Koppen