General Announcements & Updates
Release Cadence
The team has been improving our release cadence, having released two new binaries 1.2.0 followed by 1.2.1.
1.3.0 is on its way, as we test it internally before handing it off to the wider world 
We are also aiming to make releases easier to make and verify via:
- A shared signing key between the maintainers – no longer requiring @fintohaps’ key to sign the binaries directly (and @cloudhead before him).
- The introduction of canonical references will mean that tags will be available at the canonical namespace of repositories.
Canonical References
This feature, long waited, will be included in 1.3.0 – all going well. As mentioned above this will help all projects with better practices for releasing in Radicle repositories. This took a while, but hopefully it was worth the wait.
Infrastructure Improvements
The team has also improved how we manage and deploy our infrastructure. We have opted use NixOS so that we can perform infrastructure changes declaratively and without fear (thank you rollbacks).
This has made releasing to our nodes a much easier process. We also now provide IPv6 and Onion addresses for all the hosted seed nodes as part of these updates.
Contributors
The release of 1.2.0 had 16 contributors (this was a longer period) in total and 1.2.1 had 11 
We’re so thankful for everyone who provides back to the protocol stack, and we hope to keep these kind of numbers going.
Budget
On track – and cutting costs, such as removing Vercel in favour of Cloudflare.
Quarterly Objectives Updates
Roadmap Changes
Last quarter, we said we would focus on Identity Management and Node Management. In reality, this was not able to happen. The focus became improving the current experience of using Radicle and its tooling. This was a success, where we were able to improve the usage experience around synchronising with the network via the CLI. There has been a noticeable decrease in complaints around this experience 
Our upcoming roadmap is to continue on this type of track as we rethink the fundamentals of how the protocol is organised and approach it in a sans-IO fashion. Separating I/O (networking, user input, database access) from maintaining protocol state makes the architecture more extensible and easier to test. This will open up the doors for us to evolve the protocol. On top of this, it has the potential to open the gates, or should I say Windows!
We will continue to think about identity and multi-device, but not to the same degree as the above.
Hiring
The team would like to think about hiring another protocol developer, so that we can be able to work on more of these things effectively.
Upcoming
Events
- We are asked to apply for Ubuntu Summit
- Offsite in September alongside Radicle Garden team