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
After long discussion, we decided to restart from scratch as v2. So, we changed absolute_2.0 working branch to master branch and rename existing master branch with absolute_v1 branch and froze it. Please see the related change: 178221c
So, TypeScript migration work we were doing in v1 should keep going on the work in new master branch by cherry-picking patches or migrating codes from absolute_v1 branch.
Also, it's better to use absolute_v2 label for newly registered issues, until we close all legacy issues.
The text was updated successfully, but these errors were encountered:
After long discussion, we decided to restart from scratch as v2. So, we changed
absolute_2.0
working branch tomaster
branch and rename existingmaster
branch withabsolute_v1
branch and froze it. Please see the related change: 178221cSo, TypeScript migration work we were doing in v1 should keep going on the work in new
master
branch by cherry-picking patches or migrating codes fromabsolute_v1
branch.Also, it's better to use absolute_v2 label for newly registered issues, until we close all legacy issues.
The text was updated successfully, but these errors were encountered: