From Fedora Project Wiki
< Changes
(s/FIXED/CLOSED) |
(ON_QA as code completeness) |
||
Line 48: | Line 48: | ||
ASSIGNED -> accepted by FESCo with on going development | ASSIGNED -> accepted by FESCo with on going development | ||
MODIFIED -> change is substantially done and testable | MODIFIED -> change is substantially done and testable | ||
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA) | |||
CLOSED as NEXTRELEASE -> change is completed and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> |
Revision as of 11:20, 30 May 2013
Change Proposal Name
Summary
Owner
- Name: Your Name
- Email: <your email address so we can contact you, invite you to meetings, etc.>
- Release notes owner:
Current status
- Targeted release: [[Releases/<number> | Fedora <number> ]]
- Last updated: (DATE)
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Benefit to Fedora
Scope
- Proposal owners:
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)