Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added a paragraph that it's a good idea to discuss "big" enhancement before starting to implement them

...

Try surfing the documentation - if something is confusing or not clear, let us know - or better still fix it for us. All of this website is maintained in a wiki, so please go right ahead and fix things if they are wrong or contribute new documentation.

Download the code & try it out and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?

Want to do some hacking on Groovy? Try surfing the issue tracker (see below) for open issues or features that need to be implemented, take ownership of an issue and try to fix it.

...

If you can create a JUnit test case (either via Groovy or Java code) then your issue is more likely to be resolved quicker. Take a look at some of the existing unit tests cases, find one and modify it to try reproduce your problem.

Then we can add your issue to Git and then we'll know when its really fixed and we can ensure that the problem stays fixed in future releases.

...

The best workflow for this is to raise a new issue in the tracker (see below), fix the code in a branch on your forked project, and submit a pull request via the Github UI. Be sure to mention the JIRA issue id in the pull request , and to add the pull request id to the JIRA ticket so that both are tied together. This workflow is described with in more detail in a blog post here.

If you plan to contribute "big" enhancements please give everybody a few days for discussion (using the issue tracker) before you start working. This assures that you do not waste time implementing a feature that could be rejected later on.

Instead of pull request we also accept patches. Please attach these to a JIRA issue

...