The Crossroads project follows a development model similar to that of the Linux kernel. A formal release of libxs is made from the development tree "when it's ready", and all releases are considered to be production-ready.
All contributions to the Crossroads project will be reviewed and discussed with the community on the mailing list, taking at least the following points into consideration:
- Does the contribution follow the project coding style?
- Is the contribution in line with the goals of the project?
- Does the contribution introduce any regression?
- Does the change break backward compatibility?
- Does the change introduce any unwanted API, feature, or code bloat?
- Does the change have security implications?
- For new functionality, is the use-case well understood?
- Have there been any serious objections raised in the discussion?
- Are there any potential legal or patent issues with the change?
Ultimately, whether or not a contribution is accepted into the official Crossroads code base will be decided by our dear and beloved leader, Martin Sustrik.