PocketMine-MP  1.4 - API 1.10.0
 All Classes Namespaces Functions Variables Pages
/var/lib/jenkins/jobs/PocketMine-MP-doc/workspace/CONTRIBUTING.md

class ExampleClass{ const EXAMPLE_CLASS_CONSTANT = 1; public $examplePublicVariable = "defaultValue"; private $examplePrivateVariable;

public function __construct($firstArgument, &$secondArgument = null){ if($firstArgument === "exampleValue"){ //Remember to use === instead == when possible //do things }elseif($firstArgument === "otherValue"){ $secondArgument = function(){ return [ 0 => "value1", 1 => "value2", 2 => "value3", 3 => "value4", 4 => "value5", 5 => "value6", ]; } } }

} ```

RFC and Voting

Bug Tracking for Collaborators

Labels

To provide a concise bug tracking environment, prevent the issue tracker from over flowing and to keep support requests out of the bug tracker, PocketMine-MP uses a label scheme a bit different from the default GitHub Issues labels.

PocketMine-MP uses GitHub Issues Labels. There are a total of 12 labels.

Note: For future reference, labels must not be longer than 15 letters.

Categories

Category labels are prefixed by C:. Multiple category labels may be applied to a single issue(but try to keep this to a minimum and do not overuse category labels).

Pull Requests

Pull Requests are prefixed by PR:. Only one label may be applied for a Pull Request.

Status

Status labels show the status of the issue. Multiple status labels may be applied.

Miscellaneous

Miscellaneous labels are labels that show status not related to debugging that bug. The To-Do label and the Mojang label may not be applied to a single issue at the same time.

Closing Issues

To keep the bug tracker clear of non-related issues and to prevent it from overflowing, issues must be closed as soon as possible (This may sound unethical, but it is MUCH better than having the BUG TRACKER filled with SUPPORT REQUESTS and "I NEED HELP").

If an issue does not conform to the "Creating an Issue" guidelines above, the issue should be closed.

Milestones

PocketMine-MP uses GitHub Milestones to set a goal for a new release. A milestone is set on the following occasions.

A milestone must use the following format: ``` Alpha_<version_number> [release_title][release_version] ``` For example: ``` Alpha_1.4 beta2 ```