I agree. There are a lot of bugs we fixed since 4.8, some really big,
not to mention a lot of quality of life improvements. A 4.9.1 release
will be required anyway, because harm and I cant catch everything
(though I think we did pretty good). Dev releases are easy, but it takes
most of a month to get the translations depending on whose active. If we
can excite people with the release maybe we can get some more
translators. :)
Josh
On 5/9/16 4:24 AM, H.G. Muller wrote:
at we have, and when we received all .po files pertaining to it,
we just release a 4.9.1 with those. We might have bug-reports and
fixes in the mean
time as well, so it is never a bad idea to have an x.y.1 release
shortly after the x.y.0 release.
We could even adopt that as a policy for future releases. String
freezes are just not practical;
it is always better to have an item with an untranslated name in the
UI than not having
the item at all. Or postponing the release, leaving people with
unfixed bugs in the previous
version.
