From d70223cc12369089ff2a8c9b9c0a363e659bf88c Mon Sep 17 00:00:00 2001
From: Adam Weinberger The long answer is that keeping up-to-date with the GNOME
development branch is complicated. Sometimes components change
- in a way that makes portupgrade fail, or causes strange end results.
+ in a way that makes portupgrade fail, or causes strange end results.
If you plan to track the development branch, it is a good idea
to join the
- freebsd-gnome mailing list, as well as join the
- #freebsd-gnome IRC channel on FreeNode.
If all of this sounds scary, or you need a desktop that "Just Works," you should stick with the stable GNOME branch.
@@ -118,10 +118,10 @@ STRIP=It depends. If you think the problem is truly a bug with the GNOME component, you can report a bug using bug-buddy or - through the GNOME BugZilla + the GNOME BugZilla interface (NOTE: Evolution's BugZilla interface can be found here). If you think - the problem lies in the FreeBSD port, or is FreeBSD-specific, send + the problem lies in a FreeBSD port, or is FreeBSD-specific, send email to &email;@FreeBSD.org, or report the problem on the #freebsd-gnome IRC channel on FreeNode.
@@ -135,10 +135,10 @@ STRIP=How can I help with the development versions?
-Currently, we need people to test as much as possible, and file as +
Currently, we need people to test as much as possible, and to file as many good bugs as possible. We also need people with artistic skills to create some hot - screeshots.
+ screenshots.If you like coding, and you know Perl, we really need someone to help in porting @@ -146,6 +146,12 @@ STRIP= gnome-system-tools. Please contact marcus@FreeBSD.org if you are interested in helping with this.
+ +Even if you don't like working directly with code, we need reports on experiences + upgrading from GNOME &gnomever; to GNOME &gnomedevelver;; we need information on + which apps are exhibiting strange behaviour; we need to know in advance everything + that an end-user is likely to wind up scratching his or her head about in the future. +