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

release prep: clean-up obsolete information

Browse source
This commit is contained in:
Fischlurch 2015-11-02 19:41:24 +01:00
parent 9c9b31f0f8
commit 12cefe914e
8 changed files with 309 additions and 87 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/design/architecture/ExternalTreeDescription.txt → doc/design/architecture/ETD.txt
View file

@ -3,7 +3,7 @@ External Tree Description
:Author: Ichthyostega
:Date: Fall 2015
//Menu: label ETD
****************
_to symbolically represent hierarchically structured elements, without actually implementing them._

10
doc/technical/build/Dependencies.txt
View file

@ -1,7 +1,7 @@
Dependencies
============
:Author: core-devs
:Date: 5/2015
:Date: 11/2015
:toc:
@ -12,7 +12,7 @@ Lumiera shall scale with the provided Hardware,
the more RAM and the more/faster CPU's you have the better.
Nevertheless lower end 32bit machines are supported too.
Secondary targets will be other free operating systems which offer a decent Posix API. +
Secondary targets will be other free operating systems which offer a decent Posix API.
Porting to other more or less similar platforms will be possible, if -- by coincidence --
Someone(TM) helps with porting.
@ -90,9 +90,11 @@ Libraries
- libxv-dev footnote:[for the XV viewer widget `gui/output/xvdisplayer.cpp`
-- currently obsolete as of [yellow-background]#5/2015#][yellow-background]#TODO 5/2015# and X-lib
- librsvg-2.0 and librsvg2-dev for rendering Icons
- libgdl-3-0 or better through libgdlmm-3.0-2 -- the »Gnome Docking Library«footnote:[GDL isn't directly related to GNOME any more.
- libgdl-3 (3.12 or better) through libgdlmm-3 -- the »Gnome Docking Library«footnote:[GDL isn't directly related to GNOME any more.
We contributed to the improvement of this library in the past. These improvements went upstream
with GDL-2.27. At times, we used to ship our own GDL package. Right now, a recent upstream version
together with the corresponding *mm-bindings will do]
together with the corresponding *mm-bindings will do. We provide a debian package for the latter,
until they will be available in the official Debian/Ubuntu/Mint repos. But we don't have any
special requirements on these `gdlmm` bindings.]

18
doc/technical/build/LumieraDebianPackage.txt
View file

@ -12,8 +12,8 @@ packages through our own link:http://Lumiera.org/debian[Debian Apt-Repository] (
TIP: readers new to Debian packages may want to have a look into our
link:{ldoc}/user/tutorials/DebianBuilding.html[Debian build tutorial],
describing the commands for building and the structure of a Debian
(source) package in general
where we describe the commands for building and explain the structure
of a Debian (source) package in general
Package build process
@ -44,7 +44,7 @@ Actually, this lookup process at application startup is performed in two phases
transitive library dependencies, and finally shared objects, which are loaded at runtime
through the `dlopen()` call.]
Especially those libraries belonging first class to the Lumiera application are built
with a relative search path ('rpath' with $ORIGIN token). These libraries are placed
with a relative search path ('rpath' with `$ORIGIN` token). These libraries are placed
into the +modules/+ subfolder
- after successfully launching the executable, the second phase performs a lookup programmatically,
@ -69,7 +69,15 @@ Releases, Branches and Conventions
Official releases are marked by a tag on the master branch. At that point, master should be
in good shape, release documentation is polished; experimental features are removed or disabled.
Usually, we'll also fork a *release branch* at that point, featuring bugfixes only.
From here we'll merge to the *debian branch*
From here we'll merge to the **debian branch**footnote:[the 'release' branch will be merged back at
times, while the 'debian' branch won't. This 'debian' branch is published through a separate
link:git://git.lumiera.org/debian/lumiera[debian/lumiera git repository] and not merged back,
since all tweaks here are strictly for debian packaging. There might be other packaging related
repositories in the future. Yet still, the 'debian' branch is based on the same common tree
and can in therory kept in the same git repository. Contrast this to the branch 'depot', which
is also published through our 'debian/lumiera' git repository. This latter branch corresponds
to a completely separate tree and holds the administrative part of our
link:http://Lumiera.org/debian[Debian package depot] (Repository) on Lumiera.org.]
Typically the release will lead to the discovery of more or less serious bugs, which are
fixed on the release branch and backported to master. The result is a sequence of point
@ -88,7 +96,7 @@ To (re)build the debian package
-- here _RELEASE-TAG_ denotes the point in the Git history, which should become
the reference source and be packaged into the *.orig.tar.gz. Usually, it's just
sufficient to use 'master' for that purpose.
sufficient to use branch 'release' for that purpose.
Debian-Depot for installation via Apt

4
doc/technical/infra/debianDepot.txt
View file

@ -76,7 +76,7 @@ everyday usage
~~~~~~~~~~~~~~
import a package::
+reprepro -V -C experimental include squeeze lumiera_0.pre.01-1+squeeze_i386.changes+
+reprepro -V -C experimental include squeeze lumiera_0.pre.03-1+jessie_i386.changes+
+
this adds the given binary lumiera package, together with all sources and the original
tarball to the 'squeeze' repository, into the 'experimental' section
@ -103,7 +103,7 @@ want to create _yet another not so useful Git repository..._)
[NOTE]
.some special details to note in our setup
=======================================================================================================================
- each block in the 'distributions' file defines a repository for a ``distribution'' (e.g. Squeeze, Lucid, Maverick).
- each block in the 'distributions' file defines a repository for a ``distribution'' (e.g. Jessie, Trusty, Rafaela).
Within such a repo, there are sections named 'Components'.
- The _override_ files mentioned in the configuration allow to overwrite / replace arbitrary fields in the metadata of
all packages added to that distribution.

33
doc/user/tutorials/DebianBuilding.txt
View file

@ -5,7 +5,7 @@ building from source -- the »Debian Way«
:toc:
In case you're using a Debian-based system (e.g. Mint, Ubuntu...), there
is a simple alternative to the manaual compiling and installing of library
is a simple alternative to the manual compiling and installing of library
dependencies. Instead of building Lumiera from source in the classical (hard)
way, you might prefer *building from the Debian source packages*.
@ -14,7 +14,7 @@ Why -- what are the benefits?
* rely on the Debian/Ubuntu package manager for sorting out the library
and build dependencies
* install Lumiera as a first-class package, like all the other software
you're using regularily. This way, the package manager ``knows'' about
you're using regularly. This way, the package manager ``knows'' about
the library dependencies and can't mix up things due to a system upgrade.
Under some circumstances, these very benefits might be a drawback, though.
@ -43,7 +43,7 @@ deb-src http://lumiera.org/debian/ jessie experimental
+
----
sudo apt-get build-dep nobug-dev
sudo apt-get build-dep libgdl-lum-dev
sudo apt-get build-dep gdlmm-3
sudo apt-get build-dep lumiera
----
. *build* using the source package.
@ -56,10 +56,10 @@ apt-get source --compile nobug-dev
prompted for signing with your GPG key. But because you're not going to upload
the created binary packages anywhere, this step can be considered optional.
* installing the created package.
* install the created package.
+
Finally, you'll find several new +*.deb+ packages in the directory where you started
the build. You need to _install_ these packages then using the basic debian package
the build. You need to _install_ these packages then using the basic Debian package
manager `dpkg`
+
----
@ -70,7 +70,7 @@ of course, the package names, versions and architecture will vary, depending on
situation.
* repeat those steps to work your way up to the +lumiera+ package; build and install
Nobug, maybe build and install libgdl-lum and finally build and install Lumiera
Nobug, maybe build and install the GDL mm-bindings and finally build and install Lumiera
. clean up.
+
@ -78,17 +78,17 @@ You can delete the source tree used for compiling. If you never intend to
re-install the package, you could also delete the created package and source package
components after installing it. But especially when trying out development versions
it might be a good idea to stash those packages somewhere, as we're not keeping _every_
package in the online Lumiera debian depot. While any package could be reproduced
package in the online Lumiera Debian depot. While any package could be reproduced
exactly with a bit of Git knowledge, just keeping the `*.deb` might be more convenient.
*That's it* -- you're done! Debian building is convenient, isn't it?
NOTE: What follows is a background information and configuration for advanced users. +
NOTE: What follows is a background information and configuration for advanced users.
You can safely skip and ignore the remainder of this page if in doubt.
Required and recommended Debian packages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Debian package manager stores for each package not only the required prerequisites,
but also some additional _recommended_ packages: Software likely to make using the given
package more convenient or improve the usage in some way. In addition, it also stores
@ -110,11 +110,22 @@ APT::Install-Recommends "false";
^_Disclaimer:_ please be sure you understand the consequences...^
Building packages from git
~~~~~~~~~~~~~~~~~~~~~~~~~~
This tutorial describes the classic way of building a Debian package, which also is the
foundation for any shortcuts and convenience scripts. In practice, people maintaining
Debian packages happen to use various shortcuts and helper scripts to automate repetitive
tasks. One such helper especially worth mentioning is **git-buildpackage**. With a little bit
of configuration, this nifty script is able to create a full Debian package just form a
git checkout in a single shot. At Lumiera.org, we maintain all our Debian packages this
way, so the necessary configuration +debian/gbp.conf* is already in place.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
The rest of this tutorial contains some more in-depth explanations for the curious
anatomy of a debian source package
anatomy of a Debian source package
----------------------------------
Debian source packages provide a standardised way of compiling software. These
@ -171,7 +182,7 @@ It is recommended to build with normal user permissions (not as root).
Note, if several packages depend on each other, you need to give them all as list
in a single command invocation.
After having prepared the sources thusly, you need to step into the root of the
After having prepared the sources this way, you need to step into the root of the
source tree, if you want to build the whole package, or even want to tweak and
modify parts.

54
doc/user/tutorials/building.txt
View file

@ -25,7 +25,7 @@ There are two distinct methods to build:
- use Git to retrieve all source code and build the »classical way«
NOTE: just compiling Lumieara on a _Debian-based_ system (e.g. Mint, Ubuntu...)
NOTE: just compiling Lumiera on a _Debian-based_ system (e.g. Mint, Ubuntu...)
is much simpler when using the Debian source package. See the separate
link:DebianBuilding.html[tutorial page] for this footnote:[besides, there
is a separate page with general
@ -46,10 +46,10 @@ authoritative information about the build dependencies is encoded into the
link:{ldoc}/technical/build/SCons.html[build system]. Thus, when the build
system aborts, indicating that a never version of some library is required,
then usually the build system is right...]
More specifically, you'll need the GNU C/C++ compiler with C++14 support (Version >= 4.9)
More specifically, you'll need the GNU C/C\++ compiler with C++14 support (Version >= 4.9)
in addition to the following tools and libraries:
* link:http://git-scm.com/[Git VCS]
* link:http://git-scm.com/[Git] (version management system)
* link:http://www.scons.org/[SCons build system]
* link:http://www.boost.org/[Boost libraries]
* link:http://gmerlin.sourceforge.net/[GAVL library]
@ -60,7 +60,7 @@ The GUI depends on the following:
* link:http://www.gtkmm.org/en/[gtkmm]
* link:http://cgit.freedesktop.org/xorg/lib/libXv[libXv]
* link:https://wiki.gnome.org/LibRsvg[lib R SVG]
* link:https://wiki.gnome.org/LibRsvg[lib rSVG]
* link:https://git.gnome.org/browse/gdl[lib GDL]
@ -76,7 +76,9 @@ libboost-dev libboost-program-options-dev libboost-regex-dev libboost-filesystem
libgavl-dev libgtkmm-3.0-dev libgdl-3-dev librsvg2-dev libxv-dev
-------------------------------------------------------------------------------------
Optionally, you may also want to install the `gtk2-engines` package.
Ubuntu note::
some people reported you need to install the `intltool` package from the standard
Ubuntu repository (for this reason it is included in the above collection)
Build Directory
@ -121,8 +123,6 @@ git clone git://git.lumiera.org/debian/nobug
This will create a (sub)directory called nobug that contains source code. +
Compile and install NoBug with the following commands:
footnote:[this will try to install the NoBug library in `/usr/lib`,
so you will require root privileges to do so!]
------------------------------------------------------------
cd nobug
autoreconf -i
@ -133,35 +133,21 @@ make
sudo make install
------------------------------------------------------------
GDL: building and installing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GDL-mm: building and installing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE: 8/2015 the information in this paragraph is outdated!
We have switched to GTK-3 recently. Now we're able just to use the
official GDL from upstream (or your distribution). But we have also
switched to C++ bindings, and thus need a gdlmm installation, which
is not yet provided through the offial repositories on most distributions.
Thus, instead of shipping our own libGDL, now we're providing a DEB package
of gdlmm through our repository...
The *GNOME Docking library* is sometimes available through your package manager,
but we provide a suitable custom package as well; the following shows how to
build the latter
The *GNOME Docking library* is available through your your package manager,
but we additionally need the C++ bindings. Since these haven't made it into the
standard repositories yet, we provide a suitable custom package here;
the following shows how to build the latter
Version limitation::
we contributed some improvements to GDL, which are only available in upstream
versions since 2.27. Moreover, the GDL development switched meanwhile to GNOME-3
and GTK-3. Since we haven't upgraded GTK yet, we need to stick to a version prior
to this switch. If your distribution provides a 2.27 =< GDL =< 2.30, you're fine.
Otherwise we've created a special package, which doesn't interfere
with an existing (older) installation of GDL.
we rely on GTK-3 and thus need a compatible GDL-3.
Ubuntu note::
you need to install the `intltool` package from the standard Ubuntu repository
------------------------------------------------------------
git clone git://git.lumiera.org/debian/gdl
cd gdl
git clone git://git.lumiera.org/debian/gdlmm
cd gdlmm
./configure
make
sudo make install
@ -193,7 +179,7 @@ and you should get a list of the libraries, part of which should look like this:
libgdl-lum.so.0 -> /usr/local/lib/libgdl-lum.so.0.0.0
------------------------------------------------------------
or similar. The same applies to 'libgdl-lum.so.0' if you needed to build it
or similar. The same applies to other custom libraries you needed to build
explicitly for your system. If any of these libraries are not listed, you'll
have to see why before you can continue.
@ -204,7 +190,7 @@ Building Lumiera
Next, after having built and installed the external libraries, go into the
_workspace directory_ and retrieve the Lumiera source code. Thereafter, build
Lumiera by invoking the *scons* build
footnote:[more options for building with scons can be found via:`scons -h` ]
footnote:[more options for building with scons can be found via: `scons -h` ]
-----------------
git clone git://git.lumiera.org/LUMIERA
cd LUMIERA
@ -221,7 +207,7 @@ as a whole. Just invoke the +target/lumiera+ executable. The current
working directory is not particularly relevant.
After the build has finished successfully, you should be able to start Lumiera.
Currently, this will bring up the GUI, without any further functionality
Currently, this will bring up the GUI, _without any further functionality_ (!)
You should see something like this:
@ -230,7 +216,7 @@ image:{l}/images/lumiera_gui_small.png[Current Lumiera GUI Screenshot]
What's next?
------------
If you're a coder, maybe you've found something to improve...? +
If you're a coder, maybe you have found something to improve...? +
Contributing to Lumiera is easy, thanks to *Git*
-> Tutorial link:contributing.html[Contributing to Lumiera coding]

25
doc/user/tutorials/contributing.txt
View file

@ -5,9 +5,7 @@ Contributing to Lumiera
:toc:
This document is aimed at helping newcomers to contribute quickly to the
project.
This document is aimed at helping newcomers to contribute. +
There are two major obstacles faced by people new to Lumiera:
- _how_ can I contribute to Lumiera
@ -90,11 +88,11 @@ Packages normally available with your distribution::
for a Debian based system (including Mint, Ubuntu and similar flavours),
you should be able to install the necessary dependencies with the command
+
------------------------------------------------------------
-------------------------------------------------------------------------------------
sudo apt-get install build-essential scons git-core valgrind intltool \
libboost-dev libboost-program-options-dev libboost-regex-dev libboost-filesystem-dev \
libgavl-dev libgtkmm-2.4-dev librsvg2-dev libxv-dev
------------------------------------------------------------
libgavl-dev libgtkmm-3.0-dev libgdl-3-dev librsvg2-dev libxv-dev
-------------------------------------------------------------------------------------
Packages not normally part of your distribution::
there are two packages most likely not available with your operating system
distribution, so you'll need to obtain the source code for these packages
@ -111,14 +109,13 @@ mkdir build && cd build
make
sudo make install
------------------------------------------------------------
- *GDL* -- a window docking library footnote:[GDL _is_ usually available
through the standard package manager, albeit in a GTK-3 based version;
since we haven't managed to port our GUI to GTK-3, we're sticking to a
rather ancient version of the Gnome Docking Library for now]
- **mm**-bindings for *GDL* -- a window docking library footnote:[GDL itself _is_
available through the standard package manager, in a version compatible to GTK-3.
What is not yet available are the corresponding C++ bindings `gdlmm-3`]
+
------------------------------------------------------------
git clone git://git.lumiera.org/debian/gdl
cd gdl
git clone git://git.lumiera.org/debian/gdlmm
cd gdlmm
./configure
make
sudo make install
@ -239,11 +236,9 @@ fact, many user interfaces should be possible.
- The initial GUI on which considerable work has already been done has been
implemented using the GTK toolkit. However, considerable more work needs to be
done on this present GUI.
- One immediate task that needs attention is to port the current GUI from
GTK2 to GTK 3. Especially, our custom style sheet needs to be ported
- we urgently need conceptual (non-coding) contributions
* work out a coherent handling concept, in accordance with model and core
* work out a coherent UI handling concept, in accordance with model and core
* we need a concept for key bindings and focus
* we need a concept for integration with control surfaces
* we need a concept for pen based handling

250
wiki/thinkPad.ichthyo.mm
View file

@ -2172,7 +2172,7 @@
</node>
</node>
</node>
<node CREATED="1437693678626" FOLDED="true" ID="ID_1536988357" MODIFIED="1439842398635" POSITION="left" TEXT="Doku">
<node CREATED="1437693678626" FOLDED="true" ID="ID_1536988357" MODIFIED="1446480525549" POSITION="left" TEXT="Doku">
<node CREATED="1437693687650" ID="ID_1484874437" MODIFIED="1437693692821" TEXT="Sound-Systeme">
<node CREATED="1437693693617" ID="ID_955932218" LINK="https://wiki.debian.org/Sound" MODIFIED="1437693739404" TEXT="siehe die Debian-&#xdc;bersichtsseite">
<richcontent TYPE="NOTE"><html>
@ -2188,9 +2188,9 @@
</node>
</node>
</node>
<node CREATED="1439176872457" FOLDED="true" HGAP="15" ID="ID_355008543" MODIFIED="1439842393308" POSITION="left" TEXT="Plattform" VSHIFT="41">
<node CREATED="1439176872457" HGAP="15" ID="ID_355008543" MODIFIED="1446480448914" POSITION="left" TEXT="Plattform" VSHIFT="41">
<icon BUILTIN="go"/>
<node CREATED="1439176875682" HGAP="36" ID="ID_1487331591" MODIFIED="1439176889180" TEXT="Debian/Jessie" VSHIFT="42">
<node CREATED="1439176875682" HGAP="47" ID="ID_1487331591" MODIFIED="1446481367404" TEXT="Debian/Jessie" VSHIFT="60">
<node CREATED="1439176890840" FOLDED="true" ID="ID_170863947" MODIFIED="1439644328498" TEXT="Probleme">
<icon BUILTIN="button_ok"/>
<node CREATED="1439176900293" ID="ID_949460307" MODIFIED="1439176911529" TEXT="Linker rpath $ORIGIN">
@ -2599,32 +2599,252 @@
<icon BUILTIN="bell"/>
</node>
</node>
<node CREATED="1439842359711" FOLDED="true" ID="ID_1982964862" MODIFIED="1439842388500" TEXT="Paket">
<icon BUILTIN="messagebox_warning"/>
<node CREATED="1439842379420" ID="ID_1336697213" MODIFIED="1439842385655" TEXT="gtk-Abh&#xe4;ngigkeiten"/>
</node>
</node>
<node CREATED="1446356359992" HGAP="9" ID="ID_1850896628" MODIFIED="1446356445623" POSITION="left" TEXT="QA" VSHIFT="69">
<icon BUILTIN="prepare"/>
<node BACKGROUND_COLOR="#fdfdcf" COLOR="#990000" CREATED="1446356368070" ID="ID_768449868" MODIFIED="1446356423988" TEXT="ouch">
<icon BUILTIN="flag-yellow"/>
<node CREATED="1446356379653" ID="ID_1354454865" MODIFIED="1446356404198" TEXT="CHECK: typed-counter-test.cpp:329: thread_1: simpleUsageTest: (1 == myCounter.size())">
<node CREATED="1446480582168" HGAP="46" ID="ID_554745278" MODIFIED="1446481388737" TEXT="Release" VSHIFT="-5">
<node CREATED="1446480601381" ID="ID_1870415321" MODIFIED="1446480871057" TEXT="release prep: clean-up obsolete information">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
sporadischer Fehlschlag am 1.11.2015
Doku durchk&#228;mmen nach M&#252;ll
</p>
</body>
</html>
</richcontent>
<font NAME="SansSerif" SIZE="12"/>
<icon BUILTIN="full-1"/>
<node CREATED="1446482192807" ID="ID_852733328" MODIFIED="1446489451006" TEXT="Debian">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
hier nach offensichtlich obsoleter Info checken
</p>
<p>
wir kann das passieren?
<font color="#d40222">WICHTIG</font>: keine vorgreifende Infor publizieren!!!!!
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="button_ok"/>
</node>
<node CREATED="1446482445325" ID="ID_1134936512" MODIFIED="1446489442748" TEXT="Build-Tutorial">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
die explizit angegebenen Paketnamen schon mal vorchecken
</p>
<p>
die Abschnitte zu den LIbraries pr&#252;fen / umschreiben
</p>
<p>
insgesamt sorgf&#228;ltig durchlesen
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="button_ok"/>
<node CREATED="1446489425420" ID="ID_1155768637" MODIFIED="1446489430943" TEXT="building from source"/>
<node CREATED="1446489431443" ID="ID_1672115205" MODIFIED="1446489435759" TEXT="building the debian way"/>
<node CREATED="1446489436395" ID="ID_52990160" MODIFIED="1446489439070" TEXT="contributing"/>
</node>
<node CREATED="1446482485648" ID="ID_718218074" MODIFIED="1446483382066" TEXT="technical/build/Dependencies">
<icon BUILTIN="button_ok"/>
</node>
</node>
<node CREATED="1446480725508" ID="ID_789754974" MODIFIED="1446480874617" TEXT="release prep: bump version number">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
knappe Kennzeichnung des Releases in den Kommentar
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="full-2"/>
<node CREATED="1446480787391" ID="ID_1824008353" MODIFIED="1446480798862" TEXT="admin/scons/Setup.py"/>
<node CREATED="1446480787392" ID="ID_1638555946" MODIFIED="1446480803790" TEXT="data/config/setup.ini"/>
<node CREATED="1446480787392" ID="ID_619067196" MODIFIED="1446480810516" TEXT="doc/devel/Doxyfile"/>
<node CREATED="1446480787392" ID="ID_193733835" MODIFIED="1446480819004" TEXT="doc/devel/Doxyfile.browse"/>
</node>
<node CREATED="1446481181543" ID="ID_1995398229" MODIFIED="1446481331784" TEXT="R&#xfc;ck-Merge vom Release-Zweig">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
hier geht es darum, Konsistenz im Git herzustellen.
</p>
<p>
Wenn alles korrekt gemacht wurde, d&#252;rfte es hier keinen R&#252;ckflu&#223; von &#196;nderungen geben.
</p>
<p>
Bitte auch daran denken, zuerst den DEB-Zweig zu pr&#252;fen. Diesen aber nicht zur&#252;ckmergen,
</p>
<p>
denn wir wollen keine DEB-Info im Master haben!
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="full-3"/>
<node CREATED="1446481302159" ID="ID_1330024662" MODIFIED="1446481304650" TEXT="Release-Zweig"/>
<node CREATED="1446481305102" ID="ID_1191774545" MODIFIED="1446481312561" TEXT="lfd Fixes von den DEBs"/>
<node CREATED="1446481314669" ID="ID_477388235" MODIFIED="1446481329223" TEXT="Plattform-Abh&#xe4;ngigkeiten checken"/>
</node>
<node CREATED="1446480963028" ID="ID_83763074" MODIFIED="1446481179537" TEXT="Release-commit: Pre-release 0.pre.02">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
einzeilige Kennzeichnung wiederholen
</p>
<p>
die unmittelbaren Release-Dokumente durchgehen
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="full-4"/>
<node CREATED="1446481123991" ID="ID_1319204482" MODIFIED="1446481126435" TEXT="README"/>
<node CREATED="1446481126974" ID="ID_537666758" MODIFIED="1446481128522" TEXT="AUTHORS">
<node CREATED="1446481146548" ID="ID_1310945179" MODIFIED="1446481154546" TEXT="GTK-UI">
<icon BUILTIN="help"/>
</node>
<node CREATED="1446481155762" ID="ID_290411770" MODIFIED="1446481160406" TEXT="setup.ini">
<icon BUILTIN="help"/>
</node>
</node>
<node CREATED="1446481129206" ID="ID_799927356" MODIFIED="1446481131809" TEXT="LICENSE"/>
</node>
<node CREATED="1446481516578" ID="ID_552450474" MODIFIED="1446481560325" TEXT="Release-Zweig: upgrade current release to 0.pre.02">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
Merge-commit auf den Release-Zweig.
</p>
<p>
Sollte konfliktfrei sein
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="full-5"/>
</node>
<node CREATED="1446481591568" ID="ID_1120064498" MODIFIED="1446481599057" TEXT="Paketieren">
<icon BUILTIN="full-6"/>
<node CREATED="1446481606134" ID="ID_212330450" MODIFIED="1446481617041" TEXT="Merge release -&gt; deb"/>
<node CREATED="1446481618196" ID="ID_1882691551" MODIFIED="1446481637270" TEXT="Paket-Beschreibung"/>
<node CREATED="1446481637738" ID="ID_1002196753" MODIFIED="1446481639997" TEXT="Manpages"/>
<node CREATED="1446481646057" ID="ID_262549512" MODIFIED="1446481655180" TEXT="control"/>
<node CREATED="1446481655743" ID="ID_269337100" MODIFIED="1446481657219" TEXT="rules"/>
</node>
<node CREATED="1446481713984" ID="ID_1112453089" MODIFIED="1446481736903" TEXT="ausliefern">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
...das hei&#223;t bauen und hochladen
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="full-7"/>
<node CREATED="1446482059173" ID="ID_101470007" MODIFIED="1446482153165">
<richcontent TYPE="NODE"><html>
<head>
</head>
<body>
<p>
<font color="#d1013e">totmachen</font>: Debian/Wheezy (stable) : i386 and x86_64 deprecated: to be discontinued
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="messagebox_warning"/>
</node>
<node CREATED="1446482059174" ID="ID_1294670881" MODIFIED="1446482105272">
<richcontent TYPE="NODE"><html>
<head>
</head>
<body>
<p>
<b>Referenz</b>: Debian/Jessie (stable) : i386 and x86_64 (currently broken)
</p>
</body>
</html>
</richcontent>
</node>
<node CREATED="1446482059174" ID="ID_1693967692" MODIFIED="1446482059174" TEXT="Ubuntu/Trusty (14.LTS) : i386 and x86_64 (currently broken)"/>
<node CREATED="1446482059174" ID="ID_1906801117" MODIFIED="1446482059174" TEXT="Ubuntu/Vivid (15.04) : i386 (planned)"/>
<node CREATED="1446482059175" ID="ID_1107419581" MODIFIED="1446482059175" TEXT="Ubuntu/Wily (15.10) : x86_64 (planned)"/>
<node CREATED="1446482059175" ID="ID_904094860" MODIFIED="1446482059175" TEXT="Mint/Rafaela (17.2.LTS) : x86_64 (planned)"/>
<node CREATED="1446482249336" ID="ID_1088469455" MODIFIED="1446482274886" TEXT="Web/Doku aktualisieren">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
Wichtig: hier nur was wirklich gebaut ist und funktioniert!
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="messagebox_warning"/>
</node>
<node CREATED="1446481892624" ID="ID_1020531472" MODIFIED="1446482073185" TEXT="Ticket schlie&#xdf;en">
<font BOLD="true" NAME="SansSerif" SIZE="12"/>
</node>
</node>
</node>
<node CREATED="1439842359711" ID="ID_1982964862" MODIFIED="1446480466245" TEXT="Paket">
<icon BUILTIN="messagebox_warning"/>
<node CREATED="1439842379420" ID="ID_1336697213" MODIFIED="1439842385655" TEXT="gtk-Abh&#xe4;ngigkeiten"/>
<node CREATED="1446486970358" ID="ID_1758732894" MODIFIED="1446487031892" TEXT="was ist mit libXV">
<richcontent TYPE="NOTE"><html>
<head>
</head>
<body>
<p>
eigentlich war die nur notwendig f&#252;r das Video-Viewer Widget,
</p>
<p>
was nun leider tot ist. Wir haben noch keinen Ersatz. Deshalb lasse ich die Abh&#228;ngigkeit
</p>
<p>
bestehen, aber irgendwann m&#252;ssen wir das schon glattziehen
</p>
</body>
</html>
</richcontent>
<icon BUILTIN="help"/>
</node>
</node>
</node>
<node CREATED="1446356359992" HGAP="9" ID="ID_1850896628" MODIFIED="1446480440058" POSITION="left" TEXT="QA" VSHIFT="69">
<icon BUILTIN="go"/>
<node BACKGROUND_COLOR="#fdfdcf" COLOR="#990000" CREATED="1446356368070" ID="ID_768449868" MODIFIED="1446480432831" TEXT="ouch"/>
</node>
</node>
</map>