I’m happy to announce OpenOffice.org 3.1.1 beta3 packages for openSUSE. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are beta versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

As usual, we kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

The build is based on the upstream 3.1.1-rc1 release. I have marked it beta3 because upstream had found another blocker bugs in the meantime. Note that our builds are delayed after the upstream by few days by definition.

I have also fixed the OpenOffice_org-LanguageTool package to do not print the ugly messages. I do not understand why I did not see them when I tested the 0.9.9 update. I am sorry for the inconvenience.

The next build will be available about August 27, it should be 3.1.1-rc1 and I hope that it will be the final build.

I’m happy to announce OpenOffice.org 3.1.1 beta2 packages for openSUSE. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are beta versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

As usual, we kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

The next build will be available about August 21, two weeks from now, and it should be 3.1.1-rc1.The final OOo-3.1.1 packages should be available at the beginning of September.

I have vacation the following week and will not have access to the internet. I hope that the beta2 build is fine, but if you have any serious troubles with it, please report bug and downgrade to the stable build.

I’m happy to announce OpenOffice.org 3.1.1 beta1 packages for openSUSE. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are beta versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

As usual, we kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

The next build will be 3.1.1-beta2 and should be available within next two weeks. The final OOo-3.1.1 packages should be available at the beginning of September.

I’m happy to announce OpenOffice.org 3.1.1 alpha2 packages for openSUSE. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are alpha versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

The next build will be 3.1.1-beta1 and should be available 3-4 weeks from now. The final OOo-3.1.1 packages should be available at the beginning of September.

I have vacation the following two weeks and will not have access to the internet. I hope that the current alpha2 build is usable. If not, please report bugs and switch back to the stable build.

I’m happy to announce OpenOffice.org 3.1.1 alpha1 packages for openSUSE. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are alpha versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

The build for openSUSE Factory will provide also OpenOffice_org-kde4 package with an initial KDE4 integration. It is done by Roman Shtylman, an external contributor, and it is still a work in progress. I can’t build it for openSUSE-11.1 because it requires the newer Qt >= 4.5. Please be patient, Roman wants to stabilize it at first. It is a good idea because we really want to have it ready for openSUSE-11.2. Then he will look if it would be possible to port it for the older Qt and openSUSE-11.1. There are missing some useful features, so he would need to create workarounds.

Unfortunately, the packages for openSUSE Factory are still not ready in the  OpenOffice:org:UNSTABLE project because the build is blocked by rebuild of another low level packages. I have submitted the package sources also into the official openSUSE Factory. I hope that it will be available there soon.

Note that I would like to provide 3.1.1-alpha2 build within next three weeks. The final OOo-3.1.1 packages should be available at the beginning of September.

I am happy to announce that the universal Go-oo 3.1 build is available for Windows, Linux (i586, x86_64), and MAC OSX Intel. See also download and installation instructions. The builds include many upstream and Go-oo fixes.

Go-oo team hopes that you will be happy with this release. Though, any software contains bugs and we kindly ask you to report them, so that we could fixed them in the future releases. Also you could send feedback to the dev@lists.go-oo.org mailing list or contact us on irc.freenode.net, channel #go-oo.

The following OOo-3.1.1 release should be available on the beginning of September.

—

PS: I feel a bit schizophrenic. I want to blog about the openSUSE builds at planetsuse and about the universal build at planet.go-oo. Both builds are based on the same sources, so the schedule is almost the same. We only do more alpha and beta builds for openSUSE because it is so easy with the Build Service.

I wonder if the two separate announces are confusing. Should I separate the blogs even more? Any ideas?

Hmm, the best solution would be to do the universal build in the Build Service as well. Then all builds would be done at exactly the same time, they would be in the “same” repository, … It is my long term task but it will need some loving. The universal build must be done on a quite old hacky distro to work everywhere. The Windows build would require cross-compilation, …

I’m happy to announce OpenOffice.org 3.1 final packages. They are available in the Build Service OpenOffice:org:STABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The openSUSE OOo team hopes that you will be happy with this release. Though, any software contains bugs and we kindly ask you to report them, so that we could fixed them in the future releases.

Other information and plans:

We are already working on the 3.1.1 release. I would like to put the first alpha build into the OpenOffice:org:UNSTABLE project within next two weeks. The final release is planned for the beginning of September.

I’m happy to announce OpenOffice.org 3.1 rc5 packages. They are available in the Build Service OpenOffice:org:UNSTABLE project and include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are release candidates but they might still include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

Last week was hectic. We did 3 more release candidates and I think that we are really close now. We need two more days to finish QA of the last build. I believe that it will be the last one and I will be able to put the packages into the STABLE repository. It expect that the packages might appear there by the end of this week. I do not promise it but…

I have good news for Russian speaking people.  One external contributor, with the nick EGD, send me a Russian templates gallery. You might try the package OpenOffice_org-templates-ru in the OpenOffice:org:UNSTABLE project. I’ll put them into the STABLE repository after some clean up.

I’m happy to announce that OpenOffice.org 3.1 rc2 packages are available in the Build Service OpenOffice:org:UNSTABLE project. They include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are release candidates but they might still include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

I am sorry to say but we need rc3 to fix the bug #503482. The rc3 packages should be available by the end of this week. I hope that they will pass QA and I’ll be able to put the in the the STABLE repository the following week. I am sorry for another delay. We must define the feature freeze earlier the next time.

I’m happy to announce that OpenOffice.org 3.1 rc1 packages are available in the Build Service OpenOffice:org:UNSTABLE project. They include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are release candidates but they might still include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs.

Other information and plans:

We would like to add few more fixes and provide rc2 the following Monday. I hope that the rc2 build will pass QA, so I could put it into the STABLE repository as well. I am sorry that we are so delayed with stabilizing the additional features and fixes this time.