On 2017.11.24 17:09, Ralf Habacker wrote:
[snip....]
My main comment is that there has (as far as I remember) been no
official announcement about 4.8.1 - not a code freeze date, not a
string or doc freeze date, not a projected release date. Unless we
want to start all that now, I propose to release 4.8.1, and start the
proper process for release of 4.8.2.
From my previous experience with KDE projects (umbrello) I learned
a rule that documentation are freezed shortly before releasing
version x.x.0 (or x.x-1.80) so my current assumption is that the
recent documentation should be "mostly" up to date - the "whats
new" page has been updated recently by Jack.
>> Ralf
Given that we plan to do a 4.8.2 release (with minimal changes from
4.8.1,) I have already said I am happy to release 4.8.1 with
incomplete translations. In fact, if docbooks not changed by me to
4.8.1 are not fully translated, then it is likely the previous
release had the same problem.
The difference to 4.8.0 is that the 'what new' page has been updated
and is currently only been translated for 6 of 11 included languages
(54 %). The 'what's new' page is probably one of the most frequented
pages :-( The releaseme script uses a 75% completeness rate to decide
which language is included and which not. If we use that limit too,
we are below this limit.
Waiting for translation of the "What's new" page may be reasonable,
compared to waiting for the entire document. I would also think that a
complete translation of the strings is necessary to include any
translation.
When we are ready for 4.8.2, we can do a proper doc freeze and
repeat the request to the translation teams.
There are enough open bugs to thinking about a 4.8.2 release. I filed
a related ticket, see https://bugs.kde.org/show_bug.cgi?id=387280. I
learned from recent experiences with translations (Estonian
translation will be done latest in Januar, see
https://marc.info/?l=kde-i18n-doc&m=151050920321516&w=2) that it is
required to start now with 4.8.2 work for translation docbook up to
date check and fixing to have it complete in Februar 2018.
I do not remember how long it usually takes, but I think we do not want
to ask translation teams to start work before we freeze the strings and
docs, or else they may need to repeat work.
I also think the main reason for 4.8.2 is not any additional bug fixes,
but the one critical one already fixed after tagging 4.8.1. (And yes,
I've already forgotten whether that was adding the latest Quicken
versions for OFX download or fixing the loss of Yahoo for stock and
currency quoted, but both are reasonably important.) If others fixes
can be included in time, fine, but we should not wait, unless it was a
regression from 4.8.1. We need to concentrate on 5.0, and I believe
all this effort on 4.x is distracting from that goal.
Some additional notes:
1. the 4.8.1 release would be 4.8.1-1 because the source tar ball
needs to be named different as the one already uploaded
I will let others argue the details, but the 4.8.1 tarball was uploaded
before any official announcement, and without any of the usual
pre-release activities. I would just replace the existing 4.8.1
tarball with a final one, but I will not argue for it. In addition, if
we just release 4.8.1 as is, then there is no change needed for the
tarball.
2. beside the translation there is - from my point of view - a much
more important issue in the code base: I'm refering to Bug 385857
(https://bugs.kde.org/show_bug.cgi?id=385857), which makes reports
using "Convert to base currency" unreliable in case the report
interval is not daily. The related bug fix seems to be incomplete
(reported with bug 387040,
https://bugs.kde.org/show_bug.cgi?id=387040). Fixing this bug by me
will probably require some weeks from now on, because I need to dig
into the report implementation very deeply. This will delay an
official 4.8.1-1 release probably to the second week of December or
later. Fortunally this will give translators additional time to
complete translations.
I think I have said this before, and perhaps others can provide their
opinion. I think we should release 4.8.1 as it is now. There are
many bug fixes included, and a tarball has already been uploaded. We
know we need to release 4.8.2, and if we set a code freeze and string
freeze for once bug 387040 is fixed (hopefully by mid December,) and a
doc freeze once someone has confirmed which docbook files actually
need updating and I have updated them (hopefully about the same time,)
we can release some weeks after that - allowing sufficient time for
translations.
If anyone is there who has time to fix or at least can give some
information how to fix to speed up the release, be welcome.
Ralf
Jack