Internet Identity release cadence

Developers internet-identity
,
1

TL;DR

Internet Identity is moving to a faster release cadence, with up to two release proposals per week.

Dear NNS community and Internet Identity upgrade proposal reviewers,

Historically, Internet Identity has followed a weekly release cycle: release proposals were typically submitted on Fridays, with DFINITY voting on the following Monday, allowing approximately three days for community review.

Over the past year, the team has significantly increased its development velocity. This has been driven by three main factors:

  1. We addressed major sources of technical debt that had been slowing development. In particular, we migrated all applications from the legacy Internet Identity frontend to the new experience at https://id.ai and split the Internet Identity canister into separate backend and frontend canisters, improving separation of concerns, maintainability, and testability.

  2. We adopted AI-accelerated development as a standard engineering practice, improving developer productivity across implementation, testing, documentation, and code review.

  3. We expanded the team with a third full-time engineer, @MRmarioruci, who joined recently and has already been making valuable contributions.

As a result, waiting an additional three to four days before shipping improvements often no longer makes sense. To deliver features, fixes, and usability improvements to users more quickly, we plan to adopt the following release cadence:

  • Friday — Primary release proposal. This proposal is expected to be submitted nearly every week and will generally contain larger changes.

  • Monday — If no blockers are identified during community review, we will recommend that DFINITY vote in favor of adopting the primary release proposal.

  • Monday–Tuesday — Secondary release proposal. This proposal may be submitted when suitable changes are available on the main branch, such as feature-flagged functionality, small UX improvements, or other low-risk enhancements that would benefit users sooner.

  • Wednesday–Thursday — If no blockers are identified during community review, we will recommend that DFINITY vote in favor of adopting the secondary release proposal.

As a general practice, we will continue to avoid Friday deployments whenever possible.

Both primary and secondary releases may consist of a single canister upgrade proposal (for example, only the backend or only the frontend) or proposals for both canisters.

We believe this cadence strikes a good balance between rapid delivery and maintaining sufficient time for community review.

Please let us know if you have any questions, concerns, or suggestions regarding this change.

2

Cc @b3hr4d and @4eku

3

This is great news. I hope to see DFINITY take this kind of action on all proposal topics. Please don’t hesitate to implement improvements to the network.

4

Shouldn’t the currently elected grantees get compensated for more work, as it seems like more hours are needed to review proposals that fell into this topic category ? Or is this something we should ask on the dedicated Grants thread ?

5

I recommend all grantees, and anyone who wants to be a grantee, take an ownership mindset and go to DFINITY directly and ask for an opportunity to get properly compensated for performing review work. The worst thing we did with respect to community reviews was to make it a public competition for very limited resources. The truly qualified and motivated people will identify an opportunity and make a proposal for how they can fill the need. It’s DFINITY’s money and DFINITY’s decision, so why not go to them directly with a proposal.