Month of Bugs

With just over a month to go before the planned release of JBoss Cache 2.0.0 "Habanero", the JBoss Cache team would like to invite the community to take part in a Month of Bugs competition.

Contributions are welcome in all areas including bug fixes, unit tests, documentation and wiki articles, with the best ones receiving prizes delivered on the date of the final release.

What's new?

Who stands to benefit?

  • Users of JDK1.5
  • Users who want a standalone cache
  • Users who want more powerful access to nodes in the cache

Why should I take part?

The JBoss Cache team has already performed a large amount of testing during the development process and would now like to encourage users from the community to perform their own tests before the release is finalized. This helps to ensure that the software works as expected in the widest range of environments, especially your own, and you may even win a prize!

Prizes for the first 3 places are:

  1. $200 Amazon or ThinkGeek voucher + JBoss.org t-shirt
  2. $100 Amazon or ThinkGeek voucher + JBoss.org t-shirt
  3. $50 Amazon or ThinkGeek voucher + JBoss.org t-shirt

There are also runner-up prizes of JBoss.org t-shirts for places 4 to 10.

Winners will be announced at the end of the month on JBoss.org.

How do I take part?

If you wish to take part then you first need to have a jboss.com user account to login to our Issue Tracking system.

If you don't already have a jboss.com account then registration only takes a moment.

For each contribution you make that impacts the source code and documentation in the source code repository you should first create a JIRA task in the MonthOfBugs_200 component. This will allow the JBoss Cache team to judge entries and come to a final decision.

Any patches that you produce should be attached to the relevant JIRA issue together with an explanation of your work.

Wiki entries can be made as normal, providing you have a jboss.com user account. These will be collected at the end of the month and judged along with any other contributions.

Some of the things you can do to take part are:

  • Try out the new API and give feedback
  • Run custom benchmarks against the new code to validate performance
  • Run functional and soak tests to check stability
  • Review the documentation to make sure it is correct and complete
  • Write wiki articles to cover specific use cases and example configurations

Getting started