From Fedora Project Wiki
m (Sergiomb moved page Changes/MLT-7 to Changes/F36MLT-7: add target release)
No edit summary
Line 48: Line 48:
https://github.com/mltframework/mlt/issues/713
https://github.com/mltframework/mlt/issues/713


== Feedback ==
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 79: Line 77:
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->
-->
Up-to-date and latest MLT release will be delivered to Fedora users.


== Scope ==
== Scope ==

Revision as of 22:15, 17 January 2022

MLT-7

Summary

update MLT to version 7.4 (latest version)

Owner


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


Benefit to Fedora

Up-to-date and latest MLT release will be delivered to Fedora users.


Scope

  • Proposal owners:
  • Other developers:
  • 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)

Release Notes