News item at linux.org.ru - because official one just few lines without any picture :) https://www.linux.org.ru/news/multimedia/17621213 Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready. So, "main" releases will be once in half year, year but they will look more like releases, with Changelog looking less like git log :)
Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready.
+1 for testing branch. Best regards, Andrey пн, 20 мая 2024 г., 21:50 Andrew Randrianasulu via Cin < [email protected]>:
News item at linux.org.ru - because official one just few lines without any picture :)
https://www.linux.org.ru/news/multimedia/17621213
Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready. So, "main" releases will be once in half year, year but they will look more like releases, with Changelog looking less like git log :) -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready.
+2 for testing branch. (wink, wink). Actually Sam had wanted me to switch to Github as more standard and I attempted to do this quite some time ago, and ended up damaging the current Git database. Fortunately I was able to recover, but I can barely do most of what I do already, although I plan on continuing this for at least another 17 years because I do not want to see Cinelerra fade away. People come and go and I am not sure if a similarly dedicated person would want to be responsible long term for CinGG maintenance/moderation. However, when/if I find time, I will make another attempt at getting to Github and adding a "testing" branch.
P.S. although there have not been very many users testing ffmpeg 7.0, I have found no problems with it and I believe that Andrea uses it frequently also with no new reported issues. I am in the process of outlining a set of tests to run, i.e. a "test suite", when a library like ffmpeg is updated but still working on it. So, unless Andrew-R thinks it is still too soon, I was planning on checking in FFmpeg 7.0 and patches this week and making new AppImages on May 31. On Mon, May 20, 2024 at 1:42 PM Phyllis Smith <[email protected]> wrote:
Also, it was suggested that we (cinelerra-gg) can create different git
branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready.
+2 for testing branch. (wink, wink).
Actually Sam had wanted me to switch to Github as more standard and I attempted to do this quite some time ago, and ended up damaging the current Git database. Fortunately I was able to recover, but I can barely do most of what I do already, although I plan on continuing this for at least another 17 years because I do not want to see Cinelerra fade away. People come and go and I am not sure if a similarly dedicated person would want to be responsible long term for CinGG maintenance/moderation.
However, when/if I find time, I will make another attempt at getting to Github and adding a "testing" branch.
... I believe that Andrea uses it frequently also with no new reported issues.
Since you provided the patches I have always used CinGG compiled with ffmpeg 7. I have not found any problems. I have done rendering, background rendering and batch rendering without any problems. I have not done render farms. I have tried a few plugins both native and ffmpeg without problems. I have tried X11 and OpenGL-X11 without problems. Older or older projects give no problems. What tests should I do further?
пн, 20 мая 2024 г., 22:43 Phyllis Smith <[email protected]>:
Also, it was suggested that we (cinelerra-gg) can create different git
branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready.
+2 for testing branch. (wink, wink).
Actually Sam had wanted me to switch to Github as more standard and I attempted to do this quite some time ago, and ended up damaging the current Git database. Fortunately I was able to recover, but I can barely do most of what I do already, although I plan on continuing this for at least another 17 years because I do not want to see Cinelerra fade away. People come and go and I am not sure if a similarly dedicated person would want to be responsible long term for CinGG maintenance/moderation.
However, when/if I find time, I will make another attempt at getting to Github and adding a "testing" branch.
I think you can create git branch manually, from terminal. https://devconnected.com/create-git-branch/ or more descriptive official documentation: https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell first try ot on separate copy of full cingg git tree ... I hope next git push will create new branches remotely too?
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith -
Андрей Спицын