Bug 13068 - OpenShot ver 2.0 is coming
Summary: OpenShot ver 2.0 is coming
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-03-22 20:17 CET by William Kenney
Modified: 2016-05-13 22:23 CEST (History)
1 user (show)

See Also:
Source RPM: openshot-1.4.3-4.mga4.noarch.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description William Kenney 2014-03-22 20:17:21 CET 
Openshot presently exists in Mageia as Version 1.4.3. and is probably
the best video editor in Mageia. Presently the developers of OpenShot
are developing Version 2.0 with significantly enhanced capabilities.
I do not expect that Version 2.0 will make it into M5 but for sure
in M6. I believe coincoin is the maintainer of Openshot. Maybe we
can work it into M5 backports when it comes available.

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-03-30 10:39:33 CEST

Keywords: (none) => Triaged
Component: New RPM package request => RPM Packages
Assignee: bugsquad => mageia
Severity: normal => enhancement

Comment 1 Marja Van Waes 2016-05-13 18:06:35 CEST 
We still have openshot-1.4.3-9.mga6 ... don't know if anyone has time to upgrade it this weekend before the freeze

CC: (none) => marja11
Assignee: mageia => pkg-bugs

Comment 2 William Kenney 2016-05-13 21:23:49 CEST 
Thanks for thinking about this. Openshot 2.0 never got finished for a variety of reasons. Openshot 1.4.3 remains the best video editor we have for the time being.
Comment 3 Marja Van Waes 2016-05-13 22:23:57 CEST 
(In reply to William Kenney from comment #2)
> Thanks for thinking about this. Openshot 2.0 never got finished for a
> variety of reasons. Openshot 1.4.3 remains the best video editor we have for
> the time being.

Ah, I had blindly assumed it'd be finished.

Closing this request as OLD for now, it can be reopened when 2.0 is ready enough

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.