[ANN] LibreOffice 3.5.0 RC1 available

Dear Community,

The Document Foundation is happy to announce the first release
candidate of LibreOffice 3.5.0. The upcoming 3.5 will be our third
major release line, packed with many exciting new features. Please
be aware that LibreOffice 3.5.0 RC1 is not ready for production use,
you should continue to use LibreOffice 3.4.5 for that.

The release is available for Windows, Linux and Mac OS X from our QA
builds download page at

  http://www.libreoffice.org/download/pre-releases/

Should you find bugs, please report them to the FreeDesktop Bugzilla:

  https://bugs.freedesktop.org

A good way to assess the Beta3 quality is to run some specific manual
tests on it, our TCM wiki page has more details:

http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test

(and the announcement mail: http://lists.freedesktop.org/archives/libreoffice/2011-December/022464.html)

For other ways to get involved with this exciting project - you can
e.g. contribute code:

  https://www.libreoffice.org/get-involved/developers/

translate LibreOffice to your language:

  http://wiki.documentfoundation.org/Translation_for_3.5

or help with funding our operations:

  http://challenge.documentfoundation.org/

A list of known issues with 3.5.0 RC1 is available from our wiki:

  http://wiki.documentfoundation.org/Releases/3.5.0/RC1

Please find the list of changes against LibreOffice 3.5.0 beta3 here:

  http://download.documentfoundation.org/libreoffice/src/bugfixes-libreoffice-3-5-release-3.5.0.1.log

Let us close again with a BIG Thank You! to all of you having
contributed to the LibreOffice project - this release would not have
been possible without your help.

Yours,

The Document Foundation Board of Directors

Just me or that keyID lang pack is missing ?

Kaplan

Release builds (RCs) don't have keyID langpacks. Only betas have them.

Andras

It would be useful if they did, though -- at least for me, and I suppose
for Lior, and possibly others as well.
(Frankly I don't really understand why have RC1 and RC2 at all if it's
planned that they are not going to be final in any case. Why not name them
beta 4 and 5, resp?)

Regards,
Mihkel
et team

Release builds (RCs) don't have keyID langpacks. Only betas have them.

It would be useful if they did, though -- at least for me, and I suppose
for Lior, and possibly others as well.

It is not set in stone, we can change it for 3.6. My thought was that
KeyIDs would be confusing to end-users.

(Frankly I don't really understand why have RC1 and RC2 at all if it's
planned that they are not going to be final in any case. Why not name them
beta 4 and 5, resp?)

Because we need to test release configuration well.

Best regards,
Andras

It probably would be indeed. I guess it would make sense to hide key-ID
packages on download page, but list them alongside others on
http://dev-builds.libreoffice.org/pre-releases/ or such -- I think that
listing listing would confuse end-users anyway :stuck_out_tongue:

Regards,
Mihkel

I would prefer it to be in the 3.5 branch after the split to 3.5.0 branch
tomorrow.

We keep doing translation updates even between RCs, even if they will enter
the next minor release. For some of these change we need the KeyID builds.

Kaplan