Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Polarsys/UseCases"
< Polarsys
(→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. | + | Support contracts should include best practices. <br> |
Support Contracts are accessible only to Polarsys members. | Support Contracts are accessible only to Polarsys members. | ||
Revision as of 09:32, 5 April 2012
Contents
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
- Users that want professional support subscribe to a professional services offer provided by a Branded Polarsys Provider.
- 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.
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