[CONF] Apache Tuscany: Found A Bug Section (page edited)

[co...@apache.org]

Found A Bug Section (TUSCANY) edited by haleh mahbod
      Page: http://cwiki.apache.org/confluence/display/TUSCANY/Found+A+Bug+Section
   Changes: http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=55922&originalVersion=2&revisedVersion=3

Comment:
---------------------------------------------------------------------

updated text to indicate how to include JIRAs in a release

Change summary:
---------------------------------------------------------------------

updated text to indicate how to include JIRAs in a release

Change summary:
---------------------------------------------------------------------

updated text to indicate how to include JIRAs in a release

Change summary:
---------------------------------------------------------------------

updated text to indicate how to include JIRAs in a release

Change summary:
---------------------------------------------------------------------

updated text to indicate how to include JIRAs in a release

Content:
---------------------------------------------------------------------

h3. Reporting an Issue or asking for new features

*Please use Apache[JIRA|http://issues.apache.org/jira/browse/Tuscany] system to report bugs or request new features.* First time users need to create a login.

Search the existing JIRAs to see if what you want to create is already there. If not, create a new one. Make sure JIRAs are categorized correctly using JIRA categories and are created under the correct component area. Please include as much information as possible in your JIRA to help resolve the issue quicker. This can include version of the software used, platforms running on, steps to reproduce, test case, details of your requirement or even a patch if you have one. 

h3. Submitting a Patch
 
Please follow the steps below to create a patch. It will be reviewed and committed by a committer in the project.

* Perform a full build with all tests enabled for the module the fix is for. Specific build procedures vary by sub-project.  
* Confirm that the problem is fixed and include a test case where possible to help the person who is applying the patch to verify the fix.
* Generate the patch using {{svn diff File > patchfile}}
* Try to give your patch files meaningful names, including the JIRA number
* Add your patch file as an attachment to the associated JIRA issue
** Clicking on the 'Patch Available' box in the screen where the patch is being submitted will help identify available patches quicker. 

h3. How do I get my JIRAs into a release?
You can always propose a release and drive the release with the content that you want. Another way to get a JIRA into a release is by providing a patch or working with other community members (volunteers) to help you get the problem fixed. You can also help by providing test cases.

Each release is managed by a release manager. Make sure that the Release Manager is aware of why a fix to a JIRA is important to your business. In general, the best attempt is made to include as many JIRAs as possible depending on the level of community help. The voting mechanism in the JIRA system can be used to raise the importance of a JIRA to the attention of the release manager. Adding comments in the JIRA would help the release manager understand why a JIRA is important to include in a given release. 

---------------------------------------------------------------------
CONFLUENCE INFORMATION
This message is automatically generated by Confluence

Unsubscribe or edit your notifications preferences
   http://cwiki.apache.org/confluence/users/viewnotifications.action

If you think it was sent incorrectly contact one of the administrators
   http://cwiki.apache.org/confluence/administrators.action

If you want more information on Confluence, or have a bug to report see
   http://www.atlassian.com/software/confluence