You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The other alternative is we don't try to follow upstream at all and have a table in the README of which RNVI font versions map to which upstream versions
@vonovak @brentvatne @oblador
I'm input on how we should version the font packages.
One of my goals was that the version of the font packages should match upstream.
The issue is sometimes we need to update a font package when there is no upstream change, e.g. #1682
My current thought was to do something like this
I did some testing a while back, and while this approach should work, it is still reasonably ugly.
I thought about a four digit semver, but my research indicates it will break tools.
My latest thought is that if the font version is 6.7.2, our version starts at 1006.1007.1002, and we can bump the first digit.
Does anyone have a better idea or preference on the above?
The text was updated successfully, but these errors were encountered: