Originally Posted by
Thoon
Release notes are posted to the public during or after the deployment of a new update to the servers in question as part of standard process.
The process includes getting the changes together, assembling them into something that is comprehensible, sending them around for approvals, and then releasing them during or after deployment. For Live release notes there are a few more steps added, including verifying that each note passed testing (or it gets removed) and translation.
When preparing notes for Lamannia, the time between selecting a build that will be deployed and the deployment is usually short (one day, maybe two). Because of we want to get the most current build possible out the door to Lamannia, issues the developers marked as 'fixed' that make it into the release notes may have not finished their way through the testing process. The items that fail either go back for rework or get removed from the release.
But in the mean time you certainly can see things in the notes that are not working exactly as described. Were we to wait until everything was verified it would mean fewer incremental builds being deployed to Lamannia. I am against that, and try and make sure Lamannia receives a new build at least once a week during the Preview cycle.