Author: buildbot
Date: Mon Apr 10 15:29:05 2017
New Revision: 1010172
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/developer-faqs.html
websites/staging/openoffice/trunk/content/robots.txt
websites/staging/openoffice/trunk/content/social.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 10 15:29:05 2017
@@ -1 +1 @@
-1790714
+1790861
Modified: websites/staging/openoffice/trunk/content/developer-faqs.html
==============================================================================
--- websites/staging/openoffice/trunk/content/developer-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/developer-faqs.html Mon Apr 10
15:29:05 2017
@@ -187,7 +187,7 @@ e.g. issue 1234 is to use a #i1234# at t
<h2 id="where-can-i-download-developer-builds">Where can I download developer
builds?<a class="headerlink" href="#where-can-i-download-developer-builds"
title="Permanent link">¶</a></h2>
<p>Developer builds are not official releases and may be unstable. But they
can be useful to download for those who
need early access to builds, but who do not want to compile their own build.
They are announced and discussed only on the development list, as they are not
production builds. Apache OpenOffice currently has two types of development
builds: those generated by buildbots, and those manually generated/built.</p>
-<p>Apache OpenOffice makes use of buildbots for some of our environments. You
can review the Apache OpenOffice buildbot information <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info">here</a>.
Additional information on buildbot builds for linux64, window7, and linux32
can be found <a href="https://ci.apache.org/builders/">here</a>.</p>
+<p>Apache OpenOffice makes use of buildbots for some of our environments. You
can review the Apache OpenOffice buildbot information <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info">here</a>.
Additional information on buildbot builds for Windows, Linux64 and Linux32 can
be found <a
href="https://www.openoffice.org/download/devbuilds.html">here</a>.</p>
<p>Development snapshots, which are manually generated, are used as the final
step leading up to a release. These are used for final testing before an
approved release. You will also find helpful hints for specific platform
building here.</p>
<blockquote>
<p><a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds">the
Unofficial Development Snapshots page</a></p>
Modified: websites/staging/openoffice/trunk/content/robots.txt
==============================================================================
--- websites/staging/openoffice/trunk/content/robots.txt (original)
+++ websites/staging/openoffice/trunk/content/robots.txt Mon Apr 10 15:29:05
2017
@@ -1,5 +1,5 @@
# robots.txt for https://openoffice.apache.org/
User-agent: *
-Disallow: /css
-Disallow: /images
+Disallow: /css/
+Disallow: /images/
Modified: websites/staging/openoffice/trunk/content/social.html
==============================================================================
--- websites/staging/openoffice/trunk/content/social.html (original)
+++ websites/staging/openoffice/trunk/content/social.html Mon Apr 10 15:29:05
2017
@@ -125,20 +125,19 @@ h2:hover > .headerlink, h3:hover > .head
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
-<p>The Apache OpenOffice PMC coordinates access to the project's official
social networking accounts. Volunteers from the
-PMC use this accounts to inform and engage with users and the broader
OpenOffice ecosystem.</p>
+<p>The Apache OpenOffice PMC coordinates access to the project's official
social networking accounts. Volunteers from the
+PMC use these accounts to inform and engage with users and the broader
OpenOffice ecosystem.</p>
<h2 id="google">Google+<a class="headerlink" href="#google" title="Permanent
link">¶</a></h2>
-<p>Our Google+ page is <a
href="https://plus.google.com/u/0/114598373874764163668/">here</a></p>
-<h2 id="identica">Identi.ca<a class="headerlink" href="#identica"
title="Permanent link">¶</a></h2>
-<p>We can be found <a href="http://identi.ca/apacheoo">here</a> on
identi.ca</p>
+<p>Our Google+ page is <a
href="https://plus.google.com/+openoffice/">here</a></p>
+<h2 id="youtube">YouTube<a class="headerlink" href="#youtube" title="Permanent
link">¶</a></h2>
+<p>You can subscribe to our <a
href="https://www.youtube.com/channel/UC5VAaY4mqQVhNe8j7fZCEfw">YouTube</a>
channel</p>
<h2 id="twitter">Twitter<a class="headerlink" href="#twitter" title="Permanent
link">¶</a></h2>
-<p>Follow us <a href="https://twitter.com/#!/apacheoo">@ApacheOO</a> </p>
-<h2 id="hashtags">Hashtags<a class="headerlink" href="#hashtags"
title="Permanent link">¶</a></h2>
-<p>Recommended hashtags for Twitter and Identi.ca are: #aoo #apacheoo</p>
+<p>Follow us <a href="https://twitter.com/#!/apacheoo">@ApacheOO</a>
+Recommended hashtags for Twitter: #aoo #apacheoo</p>
<h2 id="facebook">Facebook<a class="headerlink" href="#facebook"
title="Permanent link">¶</a></h2>
-<p>We have a Facebook <a href="http://www.facebook.com/ApacheOO">Page</a> as
well as a <a
href="http://www.facebook.com/groups/338330086179568/">Group</a></p>
+<p>We have a Facebook <a href="https://www.facebook.com/ApacheOO">Page</a> as
well as a <a
href="https://www.facebook.com/groups/338330086179568/">Group</a></p>
<h2 id="xing">XING<a class="headerlink" href="#xing" title="Permanent
link">¶</a></h2>
-<p>Join the <a href="https://www.xing.com/net/pri344752x/aoo">Apache
OpenOffice group</a> </p>
+<p>Join the <a href="https://www.xing.com/net/pri344752x/aoo">Apache
OpenOffice group</a></p>
</div>
<div id="footera">