How the Recommended Build system should work With the introduction of the build system we hoped to give us some breathing room with development and provide a stable goal for Plugin Developers and server admins to rely on. And while I can honestly say we've achieved that, to an extent, things aren't going as I planned or expected them to. While we do expect Plugin Developers to support the latest Recommended Build, we were also hoping that they wouldn't wait until the last minute to push a compatible build out. Basically, what we expected was that plugin devs would be actively following the development of the project (maybe even having a CI setup like we have) so that they would be prepared for whenever a Recommended Build does land. Unfortunately, this doesn't seem to be the case and plugin devs are only developing for Recommended Builds instead. Although it's not realistic to expect that all Plugin Developers are always on top of new developments, it would be to everyones benefit if this was the case, especially given some changes we have planned to the Recommended Build system (see below for more information, but I suggest you read the rest of this section too). Lately I've been busy working on setting up a team of 20 or so testers that will help me ensure a Recommended Build candidate is worthy of being a Recommended Build. However, with the lack of support for non-Recommended Builds from Plugin Developers, this is a bit difficult to do. So here it is, my friendly request that Plugin Developers employ an active development model and CI setup so that myself and my testing team can include your plugin in our testing endeavors. Changes planned Since the launch of the Recommended Builds system, we've been actively on the lookout for feedback and criticisms as to how effective it is. Mostly, the feedback has been good but several people have brought up a good point that the system is too unpredictable or unstable and we agree. As such, moving forward we'll be employing a "schedule" of sorts on the Recommended Builds system. It will work as follows: every week we'll identify and communicate a Recommended Build candidate which will undergo rigorous testing. Early the following week (Monday, Tuesday or Wednesday - still to be determined) we'll promote the candidate for public consumption. This change should give both the Bukkit Team and the Plugin Developers some breathing room and a predictable schedule for Recommended Builds, as well as a weekend to work toward making their plugins RB ready. These changes should result in a better Recommended Builds system and less of a scramble to get servers and plugins updated. Naturally, this system will be skipped if there are security, exploit, critical stability fixes or Minecraft updates that we need to account for.