From 200a40b332420f94992eb39a6d0ea1cf1490ffc4 Mon Sep 17 00:00:00 2001 From: coreyg Date: Fri, 21 Nov 2014 09:30:19 +0000 Subject: Adding tuscany's website to their svn repo for svnpubsub git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1640879 13f79535-47bb-0310-9956-ffa450edef68 --- site/trunk/site-publish/sdo-cpp-found-a-bug.html | 156 +++++++++++++++++++++++ 1 file changed, 156 insertions(+) create mode 100644 site/trunk/site-publish/sdo-cpp-found-a-bug.html (limited to 'site/trunk/site-publish/sdo-cpp-found-a-bug.html') diff --git a/site/trunk/site-publish/sdo-cpp-found-a-bug.html b/site/trunk/site-publish/sdo-cpp-found-a-bug.html new file mode 100644 index 0000000000..2f2c95c45d --- /dev/null +++ b/site/trunk/site-publish/sdo-cpp-found-a-bug.html @@ -0,0 +1,156 @@ + + + + + + + + + + + + + + + Apache Tuscany : SDO CPP Found A Bug + + + + + + + + + + + + + + + +
+ + + + +   + +
+ + +
+
+ + + + + + + + + +
+  Apache Tuscany > Home > SDO Overview > SDO CPP > SDO CPP Found A Bug + + User List | Dev List | Issue Tracker   +
+ + + + + + + +
+ + +
+ +
+
+

+
General
+

Home
+License
+Get Involved
+Found a Bug?

+
+ +
SDO C++
+

SDO C++ Home
+FAQ
+Downloads
+Documentation
+Source Code

+
 +

Reporting an Issue or Asking For New Features

+ +

Please use ApacheJIRA 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.

+ +

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.
      • +
    +
    • +
+ + +

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.

+ +

How is a release done?

+

Anyone can volunteer to be a release manager and drive a release. Based on Apache guidelines, a release requires at least three PMC +1 votes and more +1s than -1s. A release can not be vetoed so a -1 does not block a release. The steps for how to create a Tuscany release are documented here

+
+
+
+ + +
+ + + + + + website stats + +
+ Copyright � 2003-2012, The Apache Software Foundation  
+ Apache Tuscany and the Apache Tuscany project logo are trademarks of The Apache Software Foundation. +
+ + + + -- cgit v1.2.3