Overview
Development is driven by tasks in JIRA, which is the authority for what gets done, by whom and by when. There are several reasons for this, some of the most important being tracking and coordination of features for a given release.
Ultimately the Terracotta product management team will decide on which features/enhancements/etc. are scheduled for each release and their relative importance, with input from developers and other sources.
 | If it's not in JIRA, it won't happen. |
You can browse Jira
or log into Jira for write access.
Getting things in JIRA
If you have something to report (bug, enhancement, architectural idea, anything), the first thing to do is search JIRA for something that already addresses it. It may be that your issue/bug/idea has been discussed before, or may already be in progress.
Bug reports or enhancement requests should be entered directly into JIRA, for deeper issues relating to design, the build system, etc. you should first get a consensus from the other developers that your idea is a good one and should be implemented; this should take place on the developer [mailing list]. Once done, please assemble the relevant comments from that discussion thread and create a new JIRA issue with your idea.
How do I know what I should be working on?
"Minor" changes should be very limited in scope and generally agreed upon based on discussions in the development [mailing list]; they should not constitute a functional change. For anything bigger than that, you should be working off of your queue in JIRA or working to get something into JIRA or helping with documentation.
Patches
When someone submits a patch there are a few things you should do before integrating it into the code base:
- Patches are only to be accepted if they are submitted as an attachment to a JIRA issue. If a prospective patch is received via another channel (like a mailing list), a developer should create a JIRA issue for it so it can be tracked.
- Verify (as much as is possible) that the contributed code is not plagiarized or protected under an existing copyright. If you are not sure or if the code either is or uses other protected code, please contact the legal department before using it.
- In addition to your own review, have a peer review the contributed code and get a consensus that the contribution is ok.
Sounds good, how do I start coding?
Click here to get started with actual code.
