[Libreoffice] Preparing announcement of the 3.4.2 release

[Cor Nouws]

[ Adding libreoffice-dev for _one_ time, so the guys there know we talk 
about this subject and can jump in if they so like ]

Hi all,

    Soon there is an announcement for the 3.4.2 release to be expected. 
So it is time to decide how we can make that version known, also for use 
in enterprises.
    To help this, I start with a little looking back at the past months 
and then explain how I look at the 3.4.2 version. And my ideas about 
announcing.

    With the various previous releases, we were involved in the 
discussions choosing how the announce the release.
    It was obvious that 3.4.0 was a great step, but not ready for use in 
(larger) production environments. As is the case for any point-zero 
release. (And apart from that, it was due to a series of reasons, not 
only the time-based release process).
    3.4.1 brought many bug fixes, but still it was not good enough to 
advise to larger deployments. However, users and companies are eager to 
profit the many improvements of the 3.4-versions. So with the 
announcement of 3.4.1, we stated that the 3.4.2 will target enterprise 
deployments.

    Now, we look at the coming 3.4.2 release. There is a large number of 
60 bugs (or more) fixed in this version.
(See this draft page:
http://wiki.documentfoundation.org/User:Nnino/Drafts/bugfixes3.4.2)
So from the issue gathering the most annoying bugs, many have been 
resolved. (See: https://bugs.freedesktop.org/show_bug.cgi?id=35673 )
    Still, there are some issues that I would have to advice my 
customers about (in my work providing professional support for 
enterprises), since they could have effect on their specific work.
    For me this does not mean that 3.4.2 does not 'target for enterprise 
deployments'. But it does not apply for any enterprise deployment too, IMHO.
    In general that is no problem, since any serious enterprise will 
test and evaluate any new version for their specific use. Our lists of 
open and fixed bugs will be helpful to them.
    The time that enterprises spent on this check, also allows for 
others to give feed back on issues that might be important for others.

    So, how could this all be reflected in the way we announce 3.4.2?
Basically, the situation IMO is that we can advise enterprises to look 
at this version to deploy. In cases where specific bugs block the use, 
there is a good change - looking at the current speed of fixing bugs) 
that the 3.4.3 release (in another month) will be the right one, so the 
preparations companies do, will be time spent useful.

   Looking forward to what others think,


-- 
  - Cor
  - http://nl.libreoffice.org