From 2e4f7351e8d45551dcfc7ff8d75f7b245e1599a5 Mon Sep 17 00:00:00 2001 From: Olivier Lacan Date: Thu, 27 Apr 2017 12:09:24 -0700 Subject: [PATCH] Remove confusing section about casing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We just say “changelog” now and we can scrap this mess. --- source/en/0.4.0/index.html.haml | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/source/en/0.4.0/index.html.haml b/source/en/0.4.0/index.html.haml index 336ec6b..fda6efd 100644 --- a/source/en/0.4.0/index.html.haml +++ b/source/en/0.4.0/index.html.haml @@ -123,20 +123,6 @@ version: 0.4.0 created by the [Gemnasium][gemnasium] team and which parses many (but not all) open source project changelogs. - ### Why do you alternate between spelling it "CHANGELOG" and "changelog"? - "CHANGELOG" is the name of the file itself. It's a bit shouty but it's a - historical convention followed by many open source projects. Other - examples of similar files include [`README`][README], [`LICENSE`][LICENSE], - and [`CONTRIBUTING`][CONTRIBUTING]. - - The uppercase naming (which in old operating systems made these files stick - to the top) is used to draw attention to them. Since they're important - metadata about the project, they could be useful to anyone intending to use - or contribute to it, much like [open source project badges][shields]. - - When I refer to a "changelog", I'm talking about the function of this - file: to log changes. - ### What about yanked releases? Yanked releases are versions that had to be pulled because of a serious bug or security issue. Often these versions don't even appear in change