Opened 6 years ago

Last modified 5 years ago

#1519 open enhancement

Managed update rollout

Reported by: zzz Owned by:
Priority: minor Milestone: undecided
Component: router/update Version: 0.9.19
Keywords: Cc:
Parent Tickets: Sensitive: no


We need a way to manage the release update process better if we need it to go slower than 36 hours. Only update a percentage, or only certain countries or OSes. Similar to what you can do on Google Play.

There are several possible reasons - to ensure the release works well, or to avoid network congestion, or tracker congestion.

It could be implemented on the server side - eche and psi could somehow "hide" the current news file from some requests, and serve the old one instead.

Or on the router side - some flag in the news file that says 'here's the latest, but please don't fetch it yet, wait a random time [x..y] before fetching.


Change History (3)

comment:1 Changed 6 years ago by zzz

Type: defectenhancement

comment:2 Changed 6 years ago by zzz

ref: http://i2p-projekt.i2p/en/docs/spec/updates
In the i2p.release section, we could have optional backoff or min/max delay params, or preferred times, or…

comment:3 Changed 5 years ago by str4d

Status: newopen
Note: See TracTickets for help on using tickets.