Absolute is a web-based O2O(Online to Offline) platform like Siren-Order for Starbucks. We are focused on creating the platform that is portable, cheaper, easier, decentralized and appless.
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.
After long discussion, we decided to restart from scratch as v2. So, we changed
absolute_2.0working branch tomasterbranch and rename existingmasterbranch withabsolute_v1branch and froze it. Please see the related change: https://github.com/lunchclass/absolute/commit/178221c65481410c9d6c3277ad17f7c91563366dSo, TypeScript migration work we were doing in v1 should keep going on the work in new
masterbranch by cherry-picking patches or migrating codes fromabsolute_v1branch.Also, it's better to use absolute_v2 label for newly registered issues, until we close all legacy issues.