An update on the Bleeding development system

Since announcing our plans to switch over to a new development system (codenamed: Bleeding) in November, we've been blown away by the amount of interest it has garnered - we're still in the early stages and already have 12+ community developers actively hacking away in the program. As we grow more satisfied with the system, we'll open it up to more volunteers but are very pleased to see the passion and the desire the community has shown to get involved.

So far, we like what we're seeing with this new system and feel that it will result in better code and quicker development through truly utilising the strength of the Bukkit community. We believe that this system has a lot of potential if used and maintained correctly and remain committed to doing so.

For those of you who would like to follow along with Bleeding development, we have a new sub-forum called Bukkit Preview where we'll be posting threads that describe each contribution Bleeding has completed to bring us to our next release build.

At this time, we only have created one thread in this new forum as it was only established recently but will be proactively using it to establish better communication with the community on what is upcoming:
http://forums.bukkit.org/threads/savedefaultconfig.52593/

Thank you for your interest in Bleeding and continued, unwavering support towards our community and project. We wouldn't be where we are without you guys!

 

What an amazing way to start the new year! Keep it up, guys!

 

Awesome!

 

Amazing!

 

Bukkit keeps suprizing me everytime xD, keep it up bukkit!

 

IMHO this is a Spout competition side effect.

 

This is as good a place as any I think to ask.

If I write a pull request for Bukkit (something relatively small, a bugfix/feature I'd need), should I still open it for the original master repository, or should I do something different to get it first into "bleeding" now that that seems to get traction?

Or asked differently, will the people that are busy in bleeding also look at those pull requests for "normal" Bukkit and if wanted/needed pull them into bleeding for testing?

 

No, this has been on the drawing board for a while now. We want to better involve the community. The tricky part was figuring out how to best go about doing that.

Small bugfixes are generally better in the main repo. Big things that need a lot of overview are better suited to a pull request made through Bleeding. Though Bleeding people regularly look at Bukkit pull requests and move them over anyway, following these guidelines will probably result in a faster pull, provided your pull has tests/ways for us to verify they do what they say they will do - nothing more, nothing less.

 

So we can get our 'max hp' plugins then???

 

Good work bukkit team.

 

So it's supposed to cause better communication with the community but we can't reply to threads in there?

 

The preview section is more about informing people what changes are coming than discussing them, but you are more than welcome to create threads talking about the features in the development section if you wish to discuss them further.

 

@Grum can correct be as I'm just re-iterating what he said on irc. Max HP on entities can no longer be adjusted because of client-related limitations.

We had to change how we handled the damage in Heroes due to this, but it is possible to internally handle damage to make it so monsters live longer/less etc.