The RC1 post on the front page reads: "On April 25th we will go ahead and release it and have it mastered to DVD unless anybody finds any significant problems with it." Should I parse this as
Bort, you can pretty much consider RC1 the final 710 release. There is an issue with USB-UIRT on 32-bit but that should be fixable via update; as soon as I verify that, symlinks from final to RC1 will be made on the mirrors.
Also, the project has become very "closed" (for an open source project). As a prime example, I spent months learning the source code and the inner workings, spent a great amount of time refactoring and fixing the X10 code that has been broken for years, and got my changes sponsored by a Pluto dev. However, when trying to get on the dev team I was pretty much told that I wasn't good enough, and would have to continue finding someone to sponsor my SVN updates (which would cut my productivity in half, which I simply don't have the time for). I have many improvements for the Lighting and Climate plugins that would be of benefit to many people.
Jon, all I asked was that you contribute more than one patch before I gave you commit access. I've contributed to a number of open source projects and not one gave me commit access after making one contribution. Admittedly you contribution was very cool and I had Dan Damron review it, but commit access means your code is of such long time high quality that I don't need to review your contributions and I can trust that you will continue to maintain the code for years into the future. I suggested that you might get another developer to review your code until he was confident enough to sponsor you for commit access. We really need all the developers we can get, but I've given commit access to people in the last few months who then disappeared entirely. I had to admit to myself that this type of churn is not good for the project, and so I instituted a relatively easy to meet bar for commit access; submit a few patches, or get sponsored by an existing svn committer. Just because you don't have commit access does not mean you can't call yourself an LMCE developer, some might even prefer that because it means they are not responsible for day to day code maintenance, the person committing your code took on that responsibility when they committed your code.