From Fedora Project Wiki
< Changes
(Created page with "= MLT-7 = == Summary == update MLT to version 7.4 (latest version) == Owner == <!-- For change proposals to qualify as self-contained, owners of all affected packages need...") |
|||
Line 42: | Line 42: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Update of MLT from v6 to v7 breaks the builds, binaries changed the name and devel files changed the location [1], authors argue that facilitates have 2 versions of MLT at same time, but I personally don't want keep to versions of MLT because MLT just 3 or 5 projects that use it, | |||
[1] | |||
https://github.com/mltframework/mlt/issues/713 | |||
== Feedback == | == Feedback == |
Revision as of 22:06, 17 January 2022
MLT-7
Summary
update MLT to version 7.4 (latest version)
Owner
- Name: Sérgio Basto
- Email: sergiomb@fedoraproject.org
Current status
- Targeted release: Fedora Linux 36
- Last updated: 2022-01-17
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Update of MLT from v6 to v7 breaks the builds, binaries changed the name and devel files changed the location [1], authors argue that facilitates have 2 versions of MLT at same time, but I personally don't want keep to versions of MLT because MLT just 3 or 5 projects that use it,
[1]
https://github.com/mltframework/mlt/issues/713
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
How To Test
User Experience
Dependencies
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)