After testing the waters with a few internal builds and some testing by the beta testing team, I'm releasing a beta version of Pale Moon to the public. Mainly, because this involves a change in development environment and compiler, and such a switch is always tricky and can result in unstable programs.

For example: I've already had to implement some changes for the user interface since it broke trying to compile the current source with the new compiler.

Important notes about the beta:
This build requires Windows Vista or later, due to toolset restrictions in Visual Studio 2012 and lack of documentation. The Final CTP has been used of Update 1, but there is no clear documentation yet to build XP compatible binaries from the command-line.
Full optimizations have been used when building this, so performance should be (close to) release levels.
Vectorization and parallelization of the code has been used. Modern processors should absolutely love this.
This beta uses Incremental Garbage Collection for javascript by default. Swtich off with javascript.options.mem.gc_incremental in case of trouble
This beta uses Azure for rendering content by default. Switch off with gfx.content.azure.enabled in case of trouble

I decided it might be a good idea to make beta 3 of the current development version of Pale Moon public as 20.3 beta 3.

The reason being that it seems to be stable, but some major changes have been made that could do with some testing "in the field" before they are finalized in the next release version.

The updates of note in this beta 3:
Change of the compiler to VS2012 Update 3 - with better binary code generation (could potentially show in benchmarks)
Change of the networking to have more aggressive failovers in case of congestion, which should further reduce any wait times if there is a networking issue.
Memory management has changed to (hopefully) reduce the memory footprint of Pale Moon in cases where lots of extensively navigated tabs are used.

This is a beta - not intended for the general public at large.
It will not update or retain an up-to-date blocklist. You will have to manually move to the release version once it is out.