Infrastructure to support "up to next LTS" certification
Our current situation is that the sales contracts and what we actually do, don't match. Our contract reflects that we only certify for 1 release of Ubuntu, but, actually, we normally keep certifying the same system in the next releases.
We should come up with a situation that balances the certification program sales market with the sales opportunity that come from certified systems. In any case, the outcome should be implemented across Canonical: Sales paperwork, contracts, Salesforce assets, certification site and processes.
The objective of this blueprint is to define an infrastructure that will enable Hardware Certification to define contracts as engagements starting from the latest stable release "up to the next LTS." This need to be supported in such a way that hardware to be certified for future releases must be unambiguous at all times.
Blueprint information
- Status:
- Complete
- Approver:
- Ara Pulido
- Priority:
- Medium
- Drafter:
- Marc Tardif
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Deferred
- Milestone target:
- None
- Started by
- Completed by
- Victor Tuson Palau
Whiteboard
== Description of Done ==
* In Hardware Certification, we should know what systems need to be certified for a release based on contracts.
* In Hardware Certification private site, it should be possible to uncheck alias names on a per certificate basis which should be reflected accordingly on the public site.
* In contracts, make sure wording and pricing is updated accordingly.
* In Canonical, communications should be dispatched to inform all stakeholders about the new contracts.
* If necessary, existing contracts should be migrated to the new meaning.
* In Salesforce, update pricing of Hardware Certification products.
* Easily generate a report to know what systems are scheduled to be certified for future releases.
== Session notes ==