Xuggler Status
Here's where you'll find the latest information on Xuggler development, transparency to our latest testing efforts, and instructions on how to donate code to the project if you want.
Latest Builds
Xuggle maintains a continuous-build server for our projects. You can check it out here for the latest and greatest builds of our software.
Visit the Xuggle Continuous Build Server »
Sometimes people get impatient waiting for an official release, and want to use the very latest (and sometimes experimental) version of Xuggler. If you're one of those people, but also don't want to build Xuggler yourself, our continuous build server makes installers out of any build that passes all Xuggler tests.Download Tip Of Tree Installers
Latest Test Results
Xuggler development is under a "test first, ask questions later" philosophy.
That means each new feature should come with self-contained tests; each bug fix should have a regression test; and all tests should be run frequently to keep us honest.
We run those tests on every checkin as part of our continuous build framework. See here for the very latest results.
On Linux systems, we run a robust memory leak and corruption test on every checkin. You can see the latest results below.
See the Latest Memory Leak & Corruption Test Results »
Donating Code to the Xuggler Project
If you'd like to donate code to the Xuggler project we're all for it. There are however certain restrictions and conventions you need to follow in order for us to accept your code:
- You must execute the Xuggle Contributor Agreement and send us a scanned copy with signature (see the agreement for where to send it to). This agreement is similar to the agreement GNU uses for user-contributed code and ensures we can continue to offer Xuggler as open-source, even if your management later decides they want to retract your code.
- You must submit test-cases (either JUnit or CPPTest) test cases for your bug fix or new feature
- You must follow the source code conventions in the Xuggler files.
- You must run the "ant run-memcheck" test suite if you add CPP code, and add appropriate tests for leaks.
- You should provide documentation of your change (really increases your chances of acceptance).
- You should shower on a regular basis; really; people prefer that.
Integration
