Commit Graph

13 Commits

Author SHA1 Message Date
Anton-Latukha 6c071d36a1
form 0.11.1 2020-12-09 18:45:44 +02:00
Guillaume Maudoux 6a91375c28
Update CHANGELOG.md
I mainly removed the line about populating builtin list as it is not relevant for users. And added the `builtins.substring` fix.
2020-12-09 10:45:05 +01:00
Anton-Latukha fbed7a656c
CHANGELOG: explain changes 2020-12-09 01:22:16 +02:00
Anton-Latukha 8c18321e74 Changelog: add Progress section 2020-11-29 14:36:11 +02:00
Anton Latukha 9d0addaa4b
CHANGELOG.md: add 0.11.0 (#749) 2020-11-02 17:57:04 +02:00
Anton-Latukha 410c325b18 cabal, CHANGELOG: 0.10.1 release, unifying the changelog
* "Misc" use was disputed, moving back to use of the "Additional" category.

* Using a (link) pattern for URLs, reasons being:
  * Including the markup into the outlines or hyperlinks considered a
    bad practice and should be used carefully.
  * The human cause:
    The reason for the changelog is so people read through it and get the info.
    Hyperlinks make text colored. Studies of readability have shown that
    people perceive the information of a brightly colored text
   much more poorly than the text of regular coloring.
    And delivering the meaning is what changelog text is for, so the
    informative text should be regularly colored.
  * The technical cause -
    the Hackage does not parse the markup inside the hyperlinks:
    https://hackage.haskell.org/package/hnix-0.10.0/changelog
    Probably because of the reason *1, but Hackage reason alone is enough.
  * Since people perceive and think about the read information mostly linearly
    and in the FIFO manner, `(link)` is put before information text, so links
    are placed in the same space and look more uniform upon reading. And upon
    reading the "link" context gets pushed first from the FIFO mind buffer and
    the further understanding the text the person is not distracted by
    sudden reading (taking-in) of the colored word "link" in the end of the
    semantically challenging text that is required to be understood.

* Dependency requirements of last major versions made literal.

* Link to `(diff)` made more obvious. While professionals tend to look for the
link to the full diff, diff under version number is ambiguous to where the
version number link leads, it can be for example: a GitHub release (where
different forms of packages are provided), diff, commit listing (as it was before
the current change), official forum post, official news... etc.

* Made `(diff)` link to point directly towards the diff.
2020-09-13 17:57:47 +03:00
Anton Latukha 5227a2d27f
CHANGELOG: 0.10.0 (#713)
* Prepare release 0.9.2

* CHANGELOG: m upd to 0.9.{2,1}

* Update changelog and version

* CHANGELOG: m upd: unification of structure, forming 0.10.1

Breaking changes into "Breaking" section.

Miscellaneous changes into "Misc" section.

Co-authored-by: Simon Jakobi <simon.jakobi@gmail.com>
2020-09-12 19:56:56 +03:00
Anton-Latukha c6f9ab81b9 CHANGELOG: 0.9.1: mv additional info into additional; explain deps 2020-07-13 19:48:34 +03:00
Anton-Latukha 37fde9b3d0 CHANGELOG: 0.9.0: m upd on GHC support status 2020-07-13 19:48:34 +03:00
Richard Marko 0b61040bee hnix.cabal: version 0.9.1 2020-07-13 19:20:31 +03:00
Richard Marko e9c9a27504 changelog: add 0.9.1 2020-07-13 19:20:31 +03:00
Simon Jakobi d9518fdd5a changelog: Clarify GHC support change in v0.9.0
v0.8.0 had already supported GHC 8.4 and 8.8, as the Hackage matrix
indicates:

https://matrix.hackage.haskell.org/#/package/hnix
2020-06-17 19:37:53 +03:00
Anton-Latukha 9ddbba595d
add CHANGELOG.md
A  CHANGELOG.md
2020-06-15 02:25:47 +03:00