...
Please keep in mind that most IzPack developers are volunteers that are not paid for developing it. We do it for fun on our free time, so please don't expect the same level of support as if we were a company (but we're doing our best to be as close to that as possible 
).
Rules for developers
- Use meaningful comments when doing a Subversion commit.
- Always mention the JIRA issue that is related to your commit (e.g., "Fix for JIRA-123").
- When doing a commit based on a patch from a contributor, make sure to mention the contributor name in the comment.
- Never commit incomplete changes (Subversion is not a backup system).
- Working on experimental changes is encouraged, but in this case use a branch.
- Like anybody else, use IzPack Enhancement Proposals and our JIRA instance.
- Don't maintain Versions.txt anymore, we will extract release notes from JIRA starting from IzPack 4.0 and beyond.
- You may do a commit without a related JIRA issue, but make sure you have a very good reason not to do so.
- Subscribe to the SCM mailing-list to get notified of SVN commits and JIRA activity.
- Do not hesitate to pick new JIRA issues: both the other developers and the issue submitter will thank you for the work!
- When you start working on an issue, don't forget to mark it as in progress so that we know that you're solving it!
Rules for contributors and issues reporters
- Always create a JIRA issue.
- If you have a patch, then attach it to the JIRA issue.
- Do not hesitate to attach screenshots and stack traces.
- Make sure you send a real diff-generated patch, not whole files or ZIPs with the modified files...
- Should you propose a new feature, make sure to attach documentation. Ideally you will have a patch for the documentation, but plain text will also do.
- Should you propose a major feature, file an IzPack Enhancement Proposal as well.
...
After IzPack 3.11.0 we will use Java 5 as the language source and target version. We will generate a Java 1.4 compatible version using Retroweaver.