flowblade icon indicating copy to clipboard operation
flowblade copied to clipboard

is flowblade abandoned?

Open purefan opened this issue 2 years ago • 5 comments

last release was 1 year ago and I see 59 unresolved issues here on github

purefan avatar Mar 31 '22 22:03 purefan

Nope! The project is still active.

The lead developer takes a break from the project every once in a while. If you look at the README.md file, you'll see this note:

"PROJECT ON BREAK I'm looking forward to continue development some time in the future, but there will not be updates for the next few months."

This is just a normal part of the project's cadence.

ratherlargerobot avatar Apr 01 '22 01:04 ratherlargerobot

Perhaps a second in command could make a minor release update with https://github.com/jliljebl/flowblade/pulls

PanderMusubi avatar Apr 24 '22 09:04 PanderMusubi

lots of commits lately, looking forward for a release before next debian freeze (january 2023)

alexmyczko avatar Aug 21 '22 20:08 alexmyczko

jliljebl, author of the project

Last contribution in 15 july 2022 Last issue comment in 12 january 2022 Last closed pull request in 5 april 2021

So the project is still active ? is a real question.

jep-fa avatar Oct 02 '22 16:10 jep-fa

@jep-fa I believe it is still active, yes. Only @jliljebl can answer authoritatively though.

alexmyczko avatar Oct 04 '22 11:10 alexmyczko

Even though I like Flowblade a lot, I have switched to https://www.shotcut.org/ since here maintenance is not what it was. Hope to return when the project is more alive again.

PanderMusubi avatar Nov 21 '22 14:11 PanderMusubi

but MLT 7 seems unsupported yet , when today 7.14 was released , anyway git diff to last tag have about 600 commits , maybe a new tag at least at pre release would be nice

sergiomb2 avatar Mar 07 '23 15:03 sergiomb2

Yes a lot of commits recently, far from dead...

alexmyczko avatar May 09 '23 13:05 alexmyczko

Project is coming fully back now with resumed communications on Issues etc. I decided to just do patches until I have 2.10 release because it turned out that I was really unable to know when I would able to release, and frankly got a bit frustrated.

Moving on I have a new set of practices like always working on branches, and dropping doing .deb packages that will prevent dropping down in this hole again. 2.10 coming in few weeks after I have gone through the issues and done a bit more testing.

jliljebl avatar May 30 '23 06:05 jliljebl