The wikis are now using the new authentication system.
If you did not migrate your account yet, visit https://idp-portal-info.suse.com/

ECO

Jump to: navigation, search

Engineering Change Order

This could be best understood as an approval for late Feature request against SUSE Linux Enterprise and therefore about ~4000/~12000 openSUSE Leap packages as well. This gets even more obvious and important by adoption of a following proposal Portal:Leap/FAQ/ClosingTheLeapGap.

Late Feature means that request is planned to be executed/implemented in a post-development phase of given release, this includes maintenance updates. Example of target milestone for given feature which would be treated as a Late Feature request would be Public Beta, Release Candidate, GMC, GM, Maintenance update.

Current process implementation happens in internal SUSE JIRA.

It's essentially a request for an approval from all stakeholders (Engineering, L3, Security, Maintenance, QA (in fact mostly Maintenance QA), documentation and Legal team.

A Feature request will not be implemented in given Service Pack unless it has an approval from all of previously mentioned stakeholders. ECO process can be generally avoided if request is submitted early in the development phase. Which is the preferred scenario for all features as introducing features late in the release introduces some risks.

Rejecting ECO does not mean that feature itself is rejected, it only means that it will not be implemented as a late feature request in given Service Pack.

ECO table (the relevant parts for reporter)

With every single community request being done I'd like to ask requester to provide as much information as possible so questions in following table can be answered.

Question Answer
L3/Maintenance ======================================
Do you expect an increased number of Maintenance updates or L3 cases because of this change? (If yes, why?) Answer
New RPMs to be added as part of this ECO Answer
RPMs to be renamed as part of this ECO Answer
Responsible team(s)/engineer(s) providing package maintenance, L3 fixes Answer
State exactly which packages will be submitted, and which packages will need to be shipped to customers Answer
How isolated is the change? Answer
API/ABI dependencies? Answer
How isolated is the change? Answer
What are the risks? Answer
For how long is the code maintained? Internal information
QA ======================================
Estimated QA effort Answer
Testing Team/s Answer
Estimated QA effort Answer