Git commit 85463c19f2b011ece59e920ac06c03f2fc749d39 by Thomas Eschenbacher.
Committed on 06/01/2017 at 13:11.
Pushed by eschenbacher into branch 'master'.
prepared for next release, v0.9.3, at 2017-01-29
M +1-1CHANGES
M +6-6README
M +1-1VERSION
M +5-5doc/en/ind
Thomas Eschenbacher ha scritto:
> Git commit 85463c19f2b011ece59e920ac06c03f2fc749d39 by Thomas Eschenbacher.
> Committed on 06/01/2017 at 13:11.
> Pushed by eschenbacher into branch 'master'.
>
> prepared for next release, v0.9.3, at 2017-01-29
>
> M +1-1CHANGES
> M +6-6README
Hi Thomas,
Am Freitag, 6. Januar 2017, 13:11:44 CET schrieb Thomas Eschenbacher:
> -2016-06-26
> -0.9.2 (Applications 16.12)
> +2017-01-29
> +0.9.3
>
Please us the releaseinfo format as described in line 128 of
https://commits.kde.org/kdoctools?path=src/template.docbook
Thanks
Hello Luigi,
sorry, I didn't know about that!
I searched through the KDE web sites, but found nothing about this topic.
For the moment I reverted the change to the docbook file only.
It is fine for me to follow the KDE release cycle and abandon the
old/own release scheme. But, to be consequent,
Am Sonntag, 8. Januar 2017, 11:26:20 CET schrieb Thomas Eschenbacher:
> 1) help_en.docbook
>
> -> is it ok and sufficient to just remove the old version, so that it
> reads like this:
> "Applications 16.12" ?
>
kwave has an own version and is released as Applications, so you should use
the schem