ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Release: rework and update the changelog

Browse source 
A handwritten changelog is considered important and
helps to single out the overall relevant achievements.
Following a proposal from the Debian policy, this summary
of development steps will now be maintained in the NEWS file.

It will be marked with the version number of Lumiera.
This commit is contained in:
Fischlurch 2025-11-22 23:51:21 +01:00
parent 6c3f0edf10
commit 8601202be5
3 changed files with 82 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

66
NEWS
View file

@ -1,6 +1,7 @@
Lumiera -- Significant Changes
==============================
:Date: 11/2015
Version: 0.pre.04~rc.1
:Date: 11/2025
*************************************************************
Lumiera is a non-linear video editing and compositing tool.
@ -8,32 +9,39 @@ Lumiera is a non-linear video editing and compositing tool.
NOTE: as of 11/2025, Lumiera is in early development stage;
it is not usable yet. This is a preview Release of a
current development snapshot in pre-alpha stage.
*************************************************************
Visit http://Lumiera.org and join the mailing list
when interested in Lumiera planning and development.
****************************************************************
In the current stage of development, the focus is primarily on the
overall integration of fundamental functionality at all levels of
the code base.
Lumiera pre-Alpha Versions
--------------------------
**This source tree doesn't yet contain a working video editing application** +
Rather, it contains the framework and technology core
of the envisioned Application ``Lumiera''.
See http://issues.lumiera.org/roadmap[Project roadmap]
As of _11/2025_ (0.pre.04)::
This version is again motivated by a series of major upgrades and clean-up.
Compilation now requires C++23 and Debian/Trixie is considered the reference
platform. The GUI is connected to the core over an asynchronous messaging
bus and the timeline display has been reshaped to accommodate flexibly
nested structures of media content, instructed by the session through
a series of _diff messages_. A scheduler has been implemented to drive
the Render Engine, but the connection to the player and UI for output
is yet unfinished.
As of _11/2015_ (0.pre.03)::
a lot of long standing maintennance work has been done. The Project switched
A lot of long standing maintenance work has been done. The Project upgraded
to C++11 and in the end even to C++14 and Debian/Jessie as reference platform,
followed by clean-up of now obsolete workarounds. On the GUI side, we largely
made the transition to GTK-3, which lead to rework of our timeline widget, not
finished yet. This work also spured an effort the connection and communication
between Proc and the UI, which is expected to be asynchroneous. Due to the
limited developer resources, work on the Engine and Player part is stalled.
followed by clean-up of workarounds now obsoleted. On the GUI side, we largely
made the transition to GTK-3, which leads to a rework of our timeline widget,
which is in progress but not finished yet. This work also spurred an effort
to reorder the connection and communication between core and the UI, which
is expected to be asynchronous. Due to the limited developer resources,
work on the Engine and Player part is stalled.
As of _10/2013_ (0.pre.02)::
the data models have been elaborated and some significant parts of the session
The data models have been elaborated and some significant parts of the session
are finished. Work has continued with time handling, a draft of the output
connection framework, a draft of the player subsystem and interfaces to the
engine and processing network. Unfortunately there was a considerable slowdown
@ -41,22 +49,28 @@ and decrease in team size, yet still the code base is growing towards 90k LOC.
No tangible progress regarding the GUI and the backend.
As of _1/2011_ (0.pre.01)::
the project has created and documented a fairly consistent design,
partially coded up -- starting from the technical foundations and working up.
The project has created and documented a fairly consistent design,
and some parts implemented -- progressing from the technical foundations.
The code base is approaching 65k LOC. Roughly half of this is test code.
The Application can be installed and started to bring up a GTK GUI framework,
but the GUI is very preliminary and not connected to core functionality.
but the GUI is rather preliminary and not connected to core functionality.
The video processing pipeline exists only in the blueprints.
As of _2/2008_::
the project has been separated completely from ``Cinelerra'', the parent project.
The project has been separated completely from Cinelerra, the parent project.
The Community, which at that time was largely identical to the Cinelerra-CV community,
choose the new project name ``Lumiera'' through a collaborative selection and vote.
The basic project infrastructure is up and running, and work on the new codebase
has started. We can show nothing beyond a test suite for some time to come.
choose the new project name **Lumiera** through a collaborative selection and vote.
The basic project infrastructure was established, and work on the new codebase
was underway. It is clear that no results other than a test suite can be shown
in the foreseeable future.
As of _7/2007_::
we started with the backend and render engine draft, some example code
complemented by several unit tests. There is a TiddlyWiki with detailed
design considerations and developer documentation and a UML model
A group of volunteers has formed to address some longstanding issues and limitations
of **Cinelerra**, which we all used for video editing tasks requiring professional quality.
The plan was to restructure some central parts of the render engine: introduce a Builder
for render pipelines and use Placements to control arrangement of clips and a unified
Data-Backend to coordinate usage of system resources. These innovations would serve
as anchor, with the intention to propose the reworked codebase as a new version
of Cinelerra, in the hope of turning Cinelerra development into a more
participatory process going forward.

1
admin/setVersion
View file

@ -40,5 +40,6 @@ rewrite doc/devel/Doxyfile 'PROJECT_NUMBER\s*=' "$VER"
rewrite doc/devel/Doxyfile.browse 'PROJECT_NUMBER\s*=' "$VER"
rewrite admin/scons/Setup.py 'VERSION\s*=' "\'$VER\'"
rewrite README 'Version:' "$VER"
rewrite NEWS 'Version:' "$VER"
echo -e "\nSUCCESSFULLY rewritten version $VER\ncheck git diff\n\n"

42
wiki/thinkPad.ichthyo.mm
View file

@ -169979,8 +169979,48 @@ that situation will improve in forseeable future.</pre>
<icon BUILTIN="yes"/>
</node>
</node>
<node BACKGROUND_COLOR="#eef0c5" COLOR="#990000" CREATED="1763770358536" ID="ID_203232523" MODIFIED="1763770402465" TEXT="die Versionsbeschreibung in ein handgeschriebenes Changelog &#xfc;berf&#xfc;hren">
<node COLOR="#338800" CREATED="1763770358536" ID="ID_203232523" MODIFIED="1763854304767" TEXT="die Versionsbeschreibung in ein handgeschriebenes Changelog &#xfc;berf&#xfc;hren">
<icon BUILTIN="yes"/>
<node BACKGROUND_COLOR="#ccb59b" COLOR="#6e2a38" CREATED="1763828021354" ID="ID_1129284385" MODIFIED="1763828191160" TEXT="grade im Zeitalter von GIt ist das wichtig">
<richcontent TYPE="NOTE"><html>
<head/>
<body>
<p>
...ein Commit-Log einer gr&#246;&#223;eren Applikation ist f&#252;r sich allein nicht aussagekr&#228;ftig; es mu&#223; in den Kontext gestellt werden durch ein offiziell verbindlich vorgegebenes Urteil wo das Projekt steht und wohin es sich bewegt.
</p>
</body>
</html></richcontent>
<font ITALIC="true" NAME="SansSerif" SIZE="14"/>
<icon BUILTIN="yes"/>
</node>
<node COLOR="#435e98" CREATED="1763828212678" ID="ID_375857423" MODIFIED="1763854212036" TEXT="Ein Statement wo das Projekt steht"/>
<node BACKGROUND_COLOR="#d2beaf" COLOR="#5c4d6e" CREATED="1763828240101" ID="ID_662477959" MODIFIED="1763854246013" TEXT="eine Charakterisierung erreichter Meilensteine">
<icon BUILTIN="hourglass"/>
</node>
<node BACKGROUND_COLOR="#c8c0b6" COLOR="#435e98" CREATED="1763828267006" ID="ID_266553263" MODIFIED="1763854259112" TEXT="hilfsweise(derzeit): Charakterisierung der preview-Releases">
<richcontent TYPE="NOTE"><html>
<head/>
<body>
<p>
<i>alle diese Preview-Releases</i>&#160;wurden bisher bedingt durch &#196;nderungen im Kontext, wie z.B. der Umstand, da&#223; ich allein die Z&#252;gel tats&#228;chlich &#252;bernommen habe, oder der Upgrade auf eine neue Refernz-Plattform und h&#246;here Sprachstandards. Zwar wollte ich das immer, aber es ist mir nie gelungen, diese Releases auch mit Erreichen eines Meilensteins zu koppeln. Zudem haben wir noch keinen der gro&#223;en Meilensteine erreicht.
</p>
</body>
</html></richcontent>
</node>
<node COLOR="#326c6b" CREATED="1763828480296" ID="ID_1858530934" MODIFIED="1763854280445" TEXT="ganz unten: ein Statemendt zu den Wurzeln des Lumiera-Projekts"/>
<node COLOR="#304c03" CREATED="1763828501853" ID="ID_633988881" MODIFIED="1763854763276">
<richcontent TYPE="NODE"><html>
<head/>
<body>
<p>
NEWS sollte neben einem Datum auch die <b>Versionsnummer</b>&#160;tragen
</p>
</body>
</html></richcontent>
<icon BUILTIN="button_ok"/>
<node COLOR="#435e98" CREATED="1763828549855" ID="ID_1372469186" MODIFIED="1763854770485" TEXT="Header-Feld definieren"/>
<node COLOR="#435e98" CREATED="1763828556872" ID="ID_1449054144" MODIFIED="1763854770488" TEXT="Skript f&#xfc;r automatisches Update erg&#xe4;nzen"/>
</node>
</node>
<node BACKGROUND_COLOR="#eef0c5" COLOR="#990000" CREATED="1763770416491" ID="ID_473314528" MODIFIED="1763770591726" TEXT="Autoren- und Lizenzinformation nochmal gr&#xfc;ndlich &#xfc;berpr&#xfc;fen">
<arrowlink COLOR="#a464b9" DESTINATION="ID_1682124476" ENDARROW="Default" ENDINCLINATION="233;-2422;" ID="Arrow_ID_1163398028" STARTARROW="None" STARTINCLINATION="774;35;"/>