THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
| Info | ||
|---|---|---|
| ||
New contributors should register account at https://issues.apache.org/jira/secure/Dashboard.jspa and send out email to project's dev list with request for contributors permissions. Committers should handle this request and grant contributor access to new community member. |
...
Tickets and Versions
Tickets are picked up by community members from a pool of unassigned and unscheduled tickets after discussion on project's dev list. Assigning tickets to a version contributor helps others to understand what will be included in next release.
JIRA issues are grouped by fixVersion field, which is an intended version of the product feature gets merged to. Everyone should make sure that after closing fixVersion is set to a proper version that actually releases the changes made in scope of the ticket.
The following page contains information on upcoming releases (draft) Release Plan.
Ticket Creation
- Every JIRA ticket should be sufficiently described.
- There should not be any tickets with title only and without description.
- If there is a discussion pertaining to the ticket, the ticket should have a link to the dev list.
...
Instructions on how to build source and binary releases can be found at DEVNOTES.txt. Please see "Ignite Release Instructions" section. On how to make official release please refer to Voting Release Process.
Workflow
There are 3 way how you can make contribution
...
Overview
Content Tools
Apps