3 ms·

https://github.com/getsentry/sentry/pull/60144 https://github.com/getsentry/sentry/pull/60144 -> https://github.com/getsentry/sentry/blob/d4d89e2fa93ad99f13d54d

https://github.com/getsentry/sentry/pull/60144 https://github.com/getsentry/sentry/pull/60144 -> https://github.com/getsentry/sentry/blob/d4d89e2fa93ad99f13d54d06d3e7df3e7753b2dc/LICENSE.md#change-license https://github.com/getsentry/sentry/blob/d4d89e2fa93ad99f13d... If they're going to all this trouble for "ambiguity," I don't know why they wouldn't further extend their custom SPDX identifier to include the "2 year" rollover, since that's one of their pearl-clutching reasons for this bullshit: https://github.com/getsentry/loose-confederation/issues/4 https://github.com/getsentry/loose-confederation/issues/4

the_mitsuhiko 3y ago
Armin from Sentry here. > I don't know why they wouldn't further extend their custom SPDX identifier to include the "2 year" rollover Unlike the target license of which there are two to chose from, the two years are not variables in the license.