From owner-svn-doc-head@FreeBSD.ORG Fri Oct 18 19:02:50 2013
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTP id 5EB6BDA8;
Fri, 18 Oct 2013 19:02:50 +0000 (UTC) (envelope-from kwm@FreeBSD.org)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mx1.freebsd.org (Postfix) with ESMTPS id 4ADD527EB;
Fri, 18 Oct 2013 19:02:50 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r9IJ2oKQ046597;
Fri, 18 Oct 2013 19:02:50 GMT (envelope-from kwm@svn.freebsd.org)
Received: (from kwm@localhost)
by svn.freebsd.org (8.14.7/8.14.5/Submit) id r9IJ2oHg046596;
Fri, 18 Oct 2013 19:02:50 GMT (envelope-from kwm@svn.freebsd.org)
Message-Id: <201310181902.r9IJ2oHg046596@svn.freebsd.org>
From: Koop Mast
Date: Fri, 18 Oct 2013 19:02:50 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r43001 - head/en_US.ISO8859-1/htdocs/gnome/docs
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 18 Oct 2013 19:02:50 -0000
Author: kwm (ports committer)
Date: Fri Oct 18 19:02:49 2013
New Revision: 43001
URL: http://svnweb.freebsd.org/changeset/doc/43001
Log:
White space cleanup. Use tabs for "level 4". And double space after full stop.
Reviewed by: rene@
Modified:
head/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml
Modified: head/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml Fri Oct 18 17:55:47 2013 (r43000)
+++ head/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml Fri Oct 18 19:02:49 2013 (r43001)
@@ -15,14 +15,14 @@
Contents
- - What are development versions of GNOME all about?
- - Should I track development versions?
- - How do I obtain development versions of GNOME stuff?
- - How do I keep everything up-to-date and in sync?
- - What should I do when something does not work?
- - How can I help with the development versions?
- - What is the current state of development GNOME on
- &os;
+ - What are development versions of GNOME all about?
+ - Should I track development versions?
+ - How do I obtain development versions of GNOME stuff?
+ - How do I keep everything up-to-date and in sync?
+ - What should I do when something does not work?
+ - How can I help with the development versions?
+ - What is the current state of development GNOME on
+ &os;
Full Text
@@ -30,40 +30,40 @@
-
-
What are development versions of GNOME all about?
+ What are development versions of GNOME all about?
- The development versions are the packages released by the GNOME
- project that will eventually become the stable (release) versions.
+
The development versions are the packages released by the GNOME
+ project that will eventually become the stable (release) versions.
There are three working branches of GNOME development:
-
- - STABLE - The applications and libraries in the stable
+
+ - STABLE - The applications and libraries in the stable
branch are considered "release quality," and are the versions that
appear in the &os; ports tree. The current stable version is
GNOME &gnomever;.
- - DEVELOPMENT - In between stable releases are development
- releases. Traditionally, GNOME development releases have odd minor
+
- DEVELOPMENT - In between stable releases are development
+ releases. Traditionally, GNOME development releases have odd minor
numbers (e.g. 2.3, &gnomedevelver;, 3.(n*2)-1). Development releases will
become stable releases, and move from alpha to beta quality during
- their lifecycle. The development releases need testing by &os;
+ their lifecycle. The development releases need testing by &os;
users to minimize the number of surprises when the new stable
versions are committed to the &os; SVN tree. This document is
about the development branch. At any time the development branch for &os;
might be based of a stable GNOME release. However it will be tagged
"development" here if it is the version that is work in progress by the &os;
- GNOME team. The current development branch for &os; is GNOME &gnomedevelver;.
+ GNOME team. The current development branch for &os; is GNOME &gnomedevelver;.
- GIT - Often newer-than-new, the GIT master versions of GNOME
- applications and libraries are alpha quality, or often completely
- unbuildable. The &os; GNOME project pays attention to, but
+ applications and libraries are alpha quality, or often completely
+ unbuildable. The &os; GNOME project pays attention to, but
does not track the alpha quality code.
-
+
- Should I track GNOME development versions?
+ Should I track GNOME development versions?
- If you are looking for a stable environment, absolutely not. Please
- only track the GNOME &gnomedevelver; branch if you wish to help identify bugs
+
If you are looking for a stable environment, absolutely not. Please
+ only track the GNOME &gnomedevelver; branch if you wish to help identify bug
and improve the &os; GNOME project. You will find little
sympathy if a development-quality GNOME application eats your
homework.
@@ -71,21 +71,21 @@
- How do I obtain the development versions of GNOME stuff?
+ How do I obtain the development versions of GNOME stuff?
- Marcus maintains a
+
Marcus maintains a
SVN repository where all the development versions of
the GNOME components for &os; are housed. Instructions for
how to check out the development ports module and how to merge it
into the &os; ports tree reside on the entrance page to his SVN
repository. Please read carefully the instructions at
- http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom/.
-
+
+ http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom/.
During the development cycle, FreeBSD-specific caveats and
other useful information will be sent to
- marcuscom-devel@marcuscom.com. If you are tracking
+ marcuscom-devel@marcuscom.com. If you are tracking
the GNOME development branch, you must
subscribe to this list. You should also consider
- How do I keep everything up-to-date and in sync?
+ How do I keep everything up-to-date and in sync?
- The short answer is that you need to use the marcusmerge
+
The short answer is that you need to use the marcusmerge
script to merge the development tree with the &os; ports tree.
The marcusmerge script is available
@@ -128,16 +128,16 @@ WITH_DEBUG="yes"
#freebsd-gnome IRC channel on FreeNode
(irc.freenode.net).
- If all of this sounds scary, or you need a desktop that
- "Just Works," you should stick with the &gnomever; version that
+
If all of this sounds scary, or you need a desktop that
+ "Just Works," you should stick with the &gnomever; version that
is available in the &os; ports tree.
- What should I do when something does not work?
+ What should I do when something does not work?
- It depends. If you think the problem is truly a bug with the
+
It depends. If you think the problem is truly a bug with the
GNOME component, you can report a bug using bug-buddy or
the GNOME Bugzilla
interface. If you think the problem lies in a &os; port, or
@@ -146,14 +146,14 @@ WITH_DEBUG="yes"
or report the problem on the #freebsd-gnome IRC
channel on FreeNode.
- Please forward all relevant bug IDs to
+
Please forward all relevant bug IDs to
&email;@FreeBSD.org
so we can keep track of known issues. Thanks!
- How can I help with the development versions?
+ How can I help with the development versions?
Now that work on &gnomedevelver; has started, we need
people to install it, and test things. If you are compiling
@@ -164,10 +164,10 @@ WITH_DEBUG="yes"
- What is the current state of development GNOME on &os;?
+ What is the current state of development GNOME on &os;?
- &gnomever; is the latest version that was merged into the &os; ports tree.
- Work is currently underway to make &gnomedevelver; stable.
+ &gnomever; is the latest version that was merged into the &os; ports tree.
+ Work is currently underway to make &gnomedevelver; stable.