Skip to content

Commit

Permalink
update CHANGELOG in preparation for a new pre-release (v0.13.0a0)
Browse files Browse the repository at this point in the history
  • Loading branch information
felipesanches committed Sep 13, 2024
1 parent 679c3b9 commit b4d698f
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 4 deletions.
10 changes: 9 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,15 @@
Below are the noteworthy changes from each release.
A more detailed list of changes is available in the corresponding milestones for each release in the Github issue tracker (https://github.com/googlefonts/fontbakery/milestones?state=closed).

## Upcoming release: 0.13.0 (2024-Sep-??)
## Upcoming release: 0.13.0a0 (2024-Sep-13)
### Noteworthy code-changes
- This release adopts a new naming scheme for checks. We had reports of users getting confused by the meaning of the reverse domain names included as prefixes of check-IDs, such as **com.google.fonts**. The real meaning was that the organization identified by such domain was the first contributor of a given check implementation. But some users were confused thinking that it mean the check belong to that organization's vendor-specific profile.
- Now profiles do not include that reverse domain prefix. And do not also have the `"/check/"` keywork anymore. As an example, **com.google.fonts/check/tabular_kerning** (on the Universal profile) is now simply called **tabular_kerning**
- Also, there's been a large number of checks migrated among profiles. Mosly towards the Universal one.
- The checks themselves also moved around in the code-repository, in an attempt to remove any resemblance of profile allocation within the **/Lib/fontbakery/checks/** directory, which should be seen as a general pool of check implementations. As much as possible, profile definition should happen inside **/Lib/fontbakery/profiles** instead.
- The exception to this are the checks that are surely vendor-specific. All those were placed in sub-directories inside **Lib/fontbakery/checks/**, such as **Lib/fontbakery/checks/vendorspecific/microsoft/**.
- As this is the **"a0" pre-release**, there may be additional migrations and renames of checks, before we make an actual **v0.13.0** release. Please open an issue if you have suggestions of better names or better profile allocations.

### Changes to existing checks
#### On the Opentype profile
- **[opentype/gdef_spacing_marks]:** Clarify log-message about glyphs that seem to be spacing. (issue #4824)
Expand Down
6 changes: 3 additions & 3 deletions docs/source/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@
author = "The Font Bakery Authors"

# The short X.Y version
version = "0.12"
version = "0.13"
# The full version, including alpha/beta/rc tags
release = "0.12.10"
release = "0.13.0a0"


# -- General configuration ---------------------------------------------------
Expand Down Expand Up @@ -186,7 +186,7 @@ def linkcode_resolve(domain, info):
# as seen on this URL:
# https://github.com/fonttools/fontbakery/tree/v0.7.2/Lib/fontbakery/profiles

tree = "v0.12.10"
tree = "v0.13.0a0"
# It's not planned for us to get the line number :-(
# I had to hammer this data into the info.
if "lineno" in info:
Expand Down

0 comments on commit b4d698f

Please sign in to comment.