(openoffice-project) branch asf-site updated: Automatic Site Publish by Buildbot

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 9db982f  Automatic Site Publish by Buildbot
9db982f is described below

commit 9db982f1e0f9691ecf2d548b9f8e8f3c1c94c626
Author: buildbot <us...@infra.apache.org>
AuthorDate: Sun Sep 27 07:54:01 2026 +0000

    Automatic Site Publish by Buildbot
---
 output/blog/what-is-going-on-in-Apache-OpenOffice-development.html | 2 +-
 output/feeds/all-en.atom.xml                                       | 2 +-
 output/feeds/blog.atom.xml                                         | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/output/blog/what-is-going-on-in-Apache-OpenOffice-development.html 
b/output/blog/what-is-going-on-in-Apache-OpenOffice-development.html
index 5452f34..450cf80 100644
--- a/output/blog/what-is-going-on-in-Apache-OpenOffice-development.html
+++ b/output/blog/what-is-going-on-in-Apache-OpenOffice-development.html
@@ -170,7 +170,7 @@
 <b>What comes after that?</b>
 </p>
 <p>
-  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and &ndash; 
more importantly &ndash; would mislead our users about what they are installing.
+  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and &mdash; 
more importantly &mdash; would mislead our users about what they are installing.
 </p>
 <p>
   We have therefore retired the planned 4.2.0 and are heading directing 
towards Apache OpenOffice 5.
diff --git a/output/feeds/all-en.atom.xml b/output/feeds/all-en.atom.xml
index 1afa2fd..f124b08 100644
--- a/output/feeds/all-en.atom.xml
+++ b/output/feeds/all-en.atom.xml
@@ -19,7 +19,7 @@
 &lt;b&gt;What comes after that?&lt;/b&gt;
 &lt;/p&gt;
 &lt;p&gt;
-  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and 
&amp;ndash; more importantly &amp;ndash; would mislead our users about what 
they are installing.
+  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and 
&amp;mdash; more importantly &amp;mdash; would mislead our users about what 
they are installing.
 &lt;/p&gt;
 &lt;p&gt;
   We have therefore retired the planned 4.2.0 and are heading directing 
towards Apache OpenOffice 5.
diff --git a/output/feeds/blog.atom.xml b/output/feeds/blog.atom.xml
index 53366a8..4779e8d 100644
--- a/output/feeds/blog.atom.xml
+++ b/output/feeds/blog.atom.xml
@@ -19,7 +19,7 @@
 &lt;b&gt;What comes after that?&lt;/b&gt;
 &lt;/p&gt;
 &lt;p&gt;
-  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and 
&amp;ndash; more importantly &amp;ndash; would mislead our users about what 
they are installing.
+  The work that has landed in the development branch are no longer the kind of 
changes that fit into a point release. We are changing the platforms we build 
for, the compilers we build with, and part of the runtime we ship. The next 
logical version would be 4.2.0 but that would undersell our work and 
&amp;mdash; more importantly &amp;mdash; would mislead our users about what 
they are installing.
 &lt;/p&gt;
 &lt;p&gt;
   We have therefore retired the planned 4.2.0 and are heading directing 
towards Apache OpenOffice 5.