Comments on: OpenOffice_org 3.1 beta5 available http://lizards.opensuse.org/2009/04/21/openoffice_org-3_0_99_5/ Blogs and Ramblings of the openSUSE Members Mon, 30 Jan 2012 19:11:21 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Petr Mladek http://lizards.opensuse.org/2009/04/21/openoffice_org-3_0_99_5/#comment-908 Petr Mladek Fri, 24 Apr 2009 21:15:19 +0000 http://lizards.opensuse.org/?p=726#comment-908 It is just a naming scheme. Upstream does not use beta versions. It provides just so-called milestone builds. I think that alpha, beta, rc names are more descriptive and more tell about the quality. Release candidate should not contain any known blocker bug. The openSUSE build is delayed by few days after the upstream by definition. The openSUSE beta5 build was based on the upstream 3.1-rc1 sources but I didn't want to mark it as rc1 because I already know about the other blocker bugs => I used another beta version number in the row for it. BTW: The upstream OOo-3.1-rc1 was released 3 weeks ago. They added 30-50 fixes within the last 3 weeks. I think that the name beta was better description. Another problem is that the openSUSE build is not based on the pure upstream sources. It is based on the GO-oo sources. There are many changes. The GO-oo developers do their best to be in sync with the upstream schedule but it is not always possible. Upstream often delays releases be several weeks. It is normal that this happen also in the GO-oo project with its additional features and fixes. In each case, feel free to help us to deliver the packages on time. The GO-oo developers are still looking for more helping hands. Also I am looking for a co-packager ;-) It is just a naming scheme. Upstream does not use beta versions. It provides just so-called milestone builds. I think that alpha, beta, rc names are more descriptive and more tell about the quality. Release candidate should not contain any known blocker bug. The openSUSE build is delayed by few days after the upstream by definition. The openSUSE beta5 build was based on the upstream 3.1-rc1 sources but I didn’t want to mark it as rc1 because I already know about the other blocker bugs => I used another beta version number in the row for it.

BTW: The upstream OOo-3.1-rc1 was released 3 weeks ago. They added 30-50 fixes within the last 3 weeks. I think that the name beta was better description.

Another problem is that the openSUSE build is not based on the pure upstream sources. It is based on the GO-oo sources. There are many changes. The GO-oo developers do their best to be in sync with the upstream schedule but it is not always possible. Upstream often delays releases be several weeks. It is normal that this happen also in the GO-oo project with its additional features and fixes.

In each case, feel free to help us to deliver the packages on time. The GO-oo developers are still looking for more helping hands. Also I am looking for a co-packager ;-)

]]> By: jake http://lizards.opensuse.org/2009/04/21/openoffice_org-3_0_99_5/#comment-907 jake Fri, 24 Apr 2009 19:33:10 +0000 http://lizards.opensuse.org/?p=726#comment-907 ...beta5... couple of weeks after OO.org's rc1 released... How lang it take (time) release from openSUSE community? I can't understand - sorry! …beta5… couple of weeks after OO.org’s rc1 released…
How lang it take (time) release from openSUSE community?
I can’t understand – sorry!

]]> By: Petr Mladek http://lizards.opensuse.org/2009/04/21/openoffice_org-3_0_99_5/#comment-906 Petr Mladek Wed, 22 Apr 2009 17:24:32 +0000 http://lizards.opensuse.org/?p=726#comment-906 Just fixed it. Thanks for notice! Just fixed it. Thanks for notice!

]]> By: smspvdm http://lizards.opensuse.org/2009/04/21/openoffice_org-3_0_99_5/#comment-905 smspvdm Wed, 22 Apr 2009 16:58:08 +0000 http://lizards.opensuse.org/?p=726#comment-905 You mean first half of may, I presume? You mean first half of may, I presume?

]]>