When will we get a Recommended Build for Minecraft Beta 1.7.3? Why did this update take so long? When Minecraft Beta 1.7.3 came out, most of us on the team were not available at the time to deal with the update, causing the update to take longer than it usually would. As it was a small update, however, we were still eventually able to get a compatible build out for testing and people that like to be on the edge of technology. Unfortunately, around the same time the update came out, we were having issues with our build process, resulting in a complete halt of development and deployment and causing us to scramble to put together a temporary solution to address the issue in the meantime. While the team was able to do this in a reasonable amount of time, myself and another admin on the team was away out of town on a scheduled absence. This absence resulted in our inability to address any of the issues that came up until I got back Sunday evening, including our lack of communication which I'll explain in more detail later on in this article. So, having said all that, why isn't there a Recommended Build yet? Well, after Minecraft 1.7.2 came out, we thought that the rapid-fire Minecraft updates were done with and we could continue on with our usual development schedule and methods. Whenever we get wind of the possibility of an update, the project is immediately put under a code freeze - no more commits, unless absolutely necessary; no pull requests are handled; no changes are made whatsoever - so that we have a stable, non-changing base to work with when making changes to our code to make things compatible with the update that eventually comes out. Since we were under the impression the updates had ceased, we were slowly unfreezing the code and allowing commits once again. Unfortunately, as Minecraft 1.7.3 has come out since then, this has left the project in a messy state that isn't exactly suitable for promotion of a Recommended Build. Once we've cleaned things up again and addressed any issues that have come up through testing, we'll have a Recommended Build out soon after. Why did it take so long for an announcement to be made about the status of the update? Quite a few of you within the community have expressed concerns regarding the lack of communication on our end, to which I completely, and wholeheartedly agree. Truth be told, this last Minecraft update couldn't have come out at a worse time: quite a few of us on the team were not available over the weekend as we each had plans to go out of town, leaving many of us without access to internet or any ability to communicate any news with the community. Had we been able to communicate with you, I assure you we would have done so. We did not mean to leave you in the dark and sincerely apologise for doing so. We recognise that many people who came from hMod were not happy with the lack of communication between the development team and the community and addressing this issue was one of the main reasons I started up Bukkit with Dinnerbone. We completely understand that people have grown to depend on us to keep their servers up to date in a timely fashion and are very thankful for the patience everyone has shown while waiting for an update from us. To that end, we hope this post explains things thoroughly enough to show you that we appreciate your support and are still actively working hard on Bukkit. Lastly, since we know that some of you will ask anyway: yes we do have access to the Minecraft source, however we are not able to use the source to update CraftBukkit as their formats are incompatible. Our speedy updates are the result of a lot of experience and fine-tuning the update process we have, not due to having the source.