Today, we are ready to share these improvements with you with 4.2 dev 1 being available for public testing (you can read about the most notable changes below). This first development snapshot marks the proper start of the new development cycle, which means in the coming weeks we will be quickly merging many changes as contributors implement new features and fix long-standing bugs. You should expect a dev snapshot every 1 or 2 weeks, depending on how stable the development branch is after any given series of merges.
Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in a case of corruption or data loss.
These final days of July mark the end of the first month of the Godot 4.2 development cycle, and things are starting to pick up steam. With Godot contributors having had a few weeks to agree on, work on, review, and approve some of the new features, bigger changes are starting to appear in the upcoming dev snapshots.
— Who's your enemy?
— The whole world.
— Who's your friend?
— The cat.
The first beta of #Mastodon 4.2.0 is now available for testing! There are too many improvements to count. See the extensive changelog and upgrade instructions here: https://github.com/mastodon/mastodon/re ... .2.0-beta1
Development is well under way for our next milestone, Godot 4.2. After our dev 2 snapshot, we kept merging new features and important bug fixes, and gathered quite a number of them — so now we’re ready for the third dev snapshot to put those under broader user testing. It’s been around a month since we started this release cycle, with roughly two months to go until 4.2 beta 1, and then another month to reach stable in early November 2023.
Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in a case of corruption or data loss.
