Jump to: navigation, search

Difference between revisions of "Polarsys/UseCases"

(Bug fix)
(Bug fix)
Line 9: Line 9:
 
# Branded Polarsys Providers must offer added value in addition to raw Polarsys added Value. This added value could be providing validated binaries that are not provided.
 
# Branded Polarsys Providers must offer added value in addition to raw Polarsys added Value. This added value could be providing validated binaries that are not provided.
  
Support contracts should include best practices. <br>
+
Support contracts should include best practices:
 +
* All patches should be given back to the Polarsys LTS branch
 +
* Or there should be a good technical or confidentiality reason explained.
 
Support Contracts are accessible only to Polarsys members.
 
Support Contracts are accessible only to Polarsys members.
  

Revision as of 09:35, 5 April 2012

Support without software change

Bug fix

How to ensure that a bug can be fixed.
Support subscription for the tools they use? => ensure quick fix

  1. Users that want professional support subscribe to a professional services offer provided by a Branded Polarsys Provider.
  2. Branded Polarsys Providers must offer added value in addition to raw Polarsys added Value. This added value could be providing validated binaries that are not provided.

Support contracts should include best practices:

  • All patches should be given back to the Polarsys LTS branch
  • Or there should be a good technical or confidentiality reason explained.

Support Contracts are accessible only to Polarsys members.

Feature Request

Configuration Management is a transverse issue to Bug Fix and Feature Requests

Two many versions tends towards a custom development model and lowers economy