Change Details

This is a meta-task to track activities related to rolling out the next version of SWHID (aka v2). This includes the following: - complete on paper spec - align with work done on new git hashes - including migration plan from/cohabitation with v1 (N.B.: we need to maintain SWHID v1 support forever anyway) - understand impact on internal microservice architecture (related to T1805) - keep correspondence with v1 (there may be multiple v2 for one v1!) - reviewed by crypto experts

This is a meta-task to track activities related to rolling out the next version of SWHID (aka v2). This includes the following: - complete on paper spec - aligned with work done on new git hashes - including migration plan from/cohabitation with v1 (N.B.: we need to maintain SWHID v1 support forever anyway) - understand impact on internal microservice architecture (related to T1805, in particular use [[ https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html | SWHIDs ]] everywhere (core SWHIDs, without qualifiers)) - keep correspondence with v1 (there may be multiple v2 for one v1!) - reviewed by crypto experts

This is a meta-task to track activities related to rolling out the next version of SWHID (aka v2). This includes the following: - complete on paper spec - aligned with work done on new git hashes - including migration plan from/cohabitation with v1 (N.B.: we need to maintain SWHID v1 support forever anyway) - understand impact on internal microservice architecture (related to T1805, in particular use [[ https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html | SWHIDs ]] everywhere (core SWHIDs, without qualifiers)) - keep correspondence with v1 (there may be multiple v2 for one v1!) - reviewed by crypto experts