aboutsummaryrefslogtreecommitdiff
path: root/alacritty/src/cli.rs
diff options
context:
space:
mode:
authorChristian Duerr <contact@christianduerr.com>2020-07-31 22:31:39 +0200
committerChristian Duerr <contact@christianduerr.com>2020-07-31 21:01:36 +0000
commita2b7c9544bf91e530482241c185e1f601c56cd12 (patch)
treec96ae164929b04bb5551a71a4596c54937e820a5 /alacritty/src/cli.rs
parent6378830469be9015a09c2b01f497483d5ba77ba2 (diff)
downloadr-alacritty-a2b7c9544bf91e530482241c185e1f601c56cd12.tar.gz
r-alacritty-a2b7c9544bf91e530482241c185e1f601c56cd12.tar.bz2
r-alacritty-a2b7c9544bf91e530482241c185e1f601c56cd12.zip
Unify changelog section order
This clarifies the order of subsections in the changelog. All entries are now defined in the order `Packaging`, `Removed`, `Added`, `Changed` and `Fixed`. The sections `Security` and `Deprecated` have been removed. Since deprecation should always just be a soft deprecation with clear user warnings, it's not much different from just `Changed`, so that should make it easier to decide where to put things. The `Security` section is often not clear enough since a lot of changes might have some form of security impact depending on interpretation. Since there's unlikely to be any major security advisories from the Alacritty project, that section is not particularly useful. The `Added`, `Changed` and `Fixed` order follows the interest of the user and the impact on them. This puts the most interesting new features front and center while allowing to go for a deep dive to see if specific bugs have been fixed. The `Removed` section was put last since realistically this should not affect users. All options should be gradually deprecated and no major features should just get removed. So most of the time this will just list deprecated features that are now completely removed, which usually means there's no impact for users that updated from the last version.
Diffstat (limited to 'alacritty/src/cli.rs')
0 files changed, 0 insertions, 0 deletions