$TITLEA very short description. This text, in addition to a number that is assigned later, will identify the QIP.
Draft, accepted, rejected, final, deferred, withdrawn, or abandoned. A QIP starts out in draft status.
You may add text to expand on the status, but keep it brief.
Draft
A short description of the proposal to orient the reader.
Describe the problem that motivates this QIP. Knowing why this improvement is important will help us understand what it is and what its priority should be.
Tell us about the solution you chose to address the problem. This should include some detail about design decisions. If the change affects user experience, provide example use scenarios.
Explain why you chose this solution and not another. If it's pertinent, list goals and non-goals of the solution.
What steps are required to implement this QIP? What Qpid components are affected? If there is new code, where will it reside in the tree?
Address any possible impact in the following areas:
- Development: Does it affect the way developers work on Qpid?
- Release: Does it require changes to the release infrastructure or process? For instance, some QIPs may require changes to the build system.
- Documentation: Does it require new documentation or changes to existing documentation?
- Configuration: Does it affect the way Qpid is configured and deployed?
- Compatibility: Does it break API or ABI compatibility with existing software?
This is the person who holds final responsibility for this QIP. It must be a human being, not a company or other group. To avoid any confusion about who is responsible, it must be one and only one person.
Please include an email address.
Some Contributor, some.contributor@example.org
A list of the people who will help implement this QIP. Include email addresses.
A version number for this document. Use the format
$MAJOR.$MINOR. For major changes, increment the former, and for minor changes such as typos, increment the latter.
1.0