Update README.md with a development status note. Also update the maintained label.

Author: chris20

README.md

@@ -3,7 +3,7 @@
 
 [![Quick Tests](https://github.com/POV-Ray/povray/actions/workflows/test_build_quick.yml/badge.svg)](https://github.com/POV-Ray/povray/actions/workflows/test_build_quick.yml)
 [![Code Analysis](https://github.com/POV-Ray/povray/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/POV-Ray/povray/actions/workflows/codeql-analysis.yml)
-[![Maintenance Status](https://img.shields.io/maintenance/yes/2021.svg)](README.md "Last edited 2021-06-26")
+[![Maintenance Status](https://img.shields.io/maintenance/yes/2024.svg)](README.md "Last edited 2024-11-03")
 
 - [License](#license)
 - [Forums](#forums)
@@ -15,6 +15,21 @@
 - [Documentation](#documentation)
 - [Contacting Us](#contacting-us)
 
+Development Status (November 2024)
+--------------------------------------
+After a long break in releases of 3.8 beta test candidates, development is resuming, though not at the
+pace of past releases. That said, we hope to have a 3.8 release ready before the end of the year.
+
+One impediment we have yet to overcome is code signing for the Windows platform. Currently we have
+no means of doing so as our previous key has expired. The difficulty is both cost and the need for
+flexibility in verifying us as an organization. Despite the fact that we have a company registered
+in Australia (Persistence of Vision Raytracer Pty. Ltd.) and it is visible on the ASIC website, it
+is our experience that the verification process gets hung up by the fact the company doesn't sell
+anything, have a street address, or have a phone number.
+
+While we do not generally sign beta releases, it is our policy that official releases for the Windows
+platform are expected to be signed.
+
 License
 --------------------------------------