2024-04-15 v1.101.3 storagenode rollout has been started (instead of continuing v1.100)
save-state-resume feature for GC filewalker 2a8d0d44a
important gc file walker fix (don’t use v1.100!)
2024-04-23: v1.102 rollout has been started
save-state-resume feature for GC filewalker (0f90f061b)
some logging changes
2024-04-24: we started testing 10Mbyte (max size) bloom filters. New enough nodes may receive these bigger BFs. (We are planning to send out backward-compatible, max=4Mb BFs as well, especially for US1.
I would prefer history in ascending time order, to easily follow the events. In order to understand the now, we need to read the past, so it would be naturaly to read the updates in chronological order.
I would prefer history in ascending time order, to easily follow
I am fine with both sort orders. But having the latest news on top, helps to understand recent changes faster, IMHO. You don’t need to scroll to down. (Eventually we will have lot of events, but we can prune it to an archive post after a while…).
Also the reverse-time order is more change-log style, where the most recent release is on top. ((But changelage doesn’t contain timestamps, so it can be confusing).
I completely agree. I think the label “History” automatically makes us want to see things in chronological order in order to see the progress. While in terms of changelog, a user is going to use the latest version of the software hence showing what is included in the latest version at the top makes sense.
I would suggest that instead of making this into a complete changelog, only the important dates+versions+info should be kept.
Ie:
2024-04-15 v1.101.3 storagenode rollout has been started (instead of continuing v1.100)
save-state-resume feature for GC filewalker 2a8d0d44a
important gc file walker fix (don’t use v1.100!)
Or in other words, “update to this version asap because we fixed so and so”.
IMHO “regular” SNOs (ie those running a couple of nodes on auto updates) don’t even have to bother with this, unless they notice something wrong (ie a version downgrade). Bigger SNOs (ie those running dozens or hundreds of nodes, manually updating) will be interested in this topic since it gives important information about edge cases (ie bigger nodes and trash).