Open felipesanches opened 4 years ago
we won't spend time wrinting a changelog describing past code-changes. But we can start documenting the new changes we make to the code from now on. I will start by documenting the textproto update from issue #258
well... sorry. I just noticed I said I would document that change on a CHANGELOG, but ended up not doing it :-P
But I still believe it is a good thing we should do.
While working on #195 I looked for a CHANGELOG.md file in order to place a note describing the change but I could not find one.
I am used to keeping such file up-to-date in FontBakery and I believe that GFTools could benefit from that practice as well.