Return-Path:
X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org
Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id D1A95CDB7
for ;
Fri, 8 Jun 2012 23:24:52 +0000 (UTC)
Received: (qmail 90323 invoked by uid 500); 8 Jun 2012 23:24:52 -0000
Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org
Received: (qmail 90295 invoked by uid 500); 8 Jun 2012 23:24:52 -0000
Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: ooo-dev@incubator.apache.org
Delivered-To: mailing list ooo-commits@incubator.apache.org
Received: (qmail 90288 invoked by uid 99); 8 Jun 2012 23:24:52 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 23:24:52 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 23:24:51 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
by eris.apache.org (Postfix) with ESMTP id 93CF02388A91
for ; Fri, 8 Jun 2012 23:24:31 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r820894 - in
/websites/staging/openofficeorg/trunk/content: ./
openofficeorg/developer-faqs.html
Date: Fri, 08 Jun 2012 23:24:31 -0000
To: ooo-commits@incubator.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120608232431.93CF02388A91@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
Author: buildbot
Date: Fri Jun 8 23:24:31 2012
New Revision: 820894
Log:
Staging update by buildbot for openofficeorg
Modified:
websites/staging/openofficeorg/trunk/content/ (props changed)
websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html
Propchange: websites/staging/openofficeorg/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 8 23:24:31 2012
@@ -1 +1 @@
-1347765
+1348280
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/developer-faqs.html Fri Jun 8 23:24:31 2012
@@ -153,10 +153,11 @@ to recognize your contribution.
You might want to start by reviewing the legacy information on OpenOffice.org
development. Or, take
-a look at information posted on the OpenOffice.org wiki.
-You don't have to be an actual committer to submit code. You can submit
-patches through the developer mailing list. Please see the mailing lists page
- for further details.
+a look at information posted on the OpenOffice.org wiki.
+Of course, you will need the source code to do anything.
+You don't have to be an actual committer to submit code. You can submit patches through
+the Apache OpenOffice Bugzilla issue reporting system. You simple need to file an issue
+and supply your patch as an attachment to the issue.
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.