os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Announce GNOME 2.13.2 for FreeBSD, and update the current development

Browse source 
status.
This commit is contained in:
Joe Marcus Clarke 2005-11-18 07:33:07 +00:00
parent 91c706c924
commit 63c2e77b09
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=26367
2 changed files with 34 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

19
en/gnome/docs/develfaq.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.37 2005/10/04 17:38:26 blackend Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.38 2005/10/04 20:06:58 hrs Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
<!ENTITY % navincludes SYSTEM "../../includes.navdevelopers.sgml"> %navincludes;
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
@ -108,7 +108,7 @@ STRIP=
<a href="http://www.marcuscom.com/marcusmerge.8.html">
here</a>. This script will merge the development ports tree
into your main ports tree. From there, you can download
the <a href="http://www.marcuscom.com/downloads/gnome_upgrade212.sh">
the <a href="http://www.marcuscom.com/downloads/gnome_upgrade214.sh">
gnome_upgrade212.sh</a> script to aid in upgrading from GNOME
&gnomever; to &gnomedevelver;. Once you are running GNOME
&gnomedevelver;, you can use <a
@ -154,22 +154,19 @@ STRIP=
&gnomedevelver; handles. We are
looking for build and run problems as well as user
experiences. If you are artistic, please start submitting
splash screens and themes for 2.12. We are also looking for
splash screens and themes for 2.14. We are also looking for
some screenshots that show off some of the new features of
GNOME 2.12.</p>
GNOME 2.14.</p>
</li>
<!-- Q7 -->
<li style="padding-bottom: 0.5em"><a name="q7"></a>
<p><b>What is the current state of development GNOME on FreeBSD?</b></p>
<!-- A7 -->
<p>GNOME 2.12 has been <a
href="http://lists.freebsd.org/pipermail/freebsd-gnome/2005-September/012190.html">
release</a>. We are waiting for FreeBSD 6.0 to be released
before we merge 2.12 into the ports tree. For now, you most
of the development warnings on this page can be ignored, and
you should feel free to install and use GNOME 2.12 on your
production desktops.</p>
<p>GNOME 2.13.2 has been release, and testing for the future
GNOME 2.14 is now underway. As usual, test ports and
<a href="faq2.html#q21">packages</a>, and report any
problems to the authorities listed above.</p>
</li>
</ol>

34
en/gnome/news.xml
View file

@ -30,27 +30,45 @@ encoding="ISO-8859-1" ?>
<month>
<name>November</name>
<day>
<name>17</name>
<event>
<title>GNOME 2.13.2 available for FreeBSD</title>
<p>The exciting new winter line of GNOME Desktops has been
released, and ports are now available for FreeBSD. GNOME
2.13.2 features three new proposed desktop modules: atomix,
fast-user-switch-applet, and gnome-screensaver, along with
Firefox 1.5 as the base for Epiphany and Yelp. Testers to
their mark,
<a href="$base/gnome/docs/develfaq.html">go!</a>
</p>
</event>
</day>
<day>
<name>5</name>
<event>
<title>GNOME 2.12.1 merged into the ports tree</title>
<p>Now that FreeBSD 6.0 is out the door, GNOME 2.12.1 has been merged
into the FreeBSD ports tree. Check out the
<p>Now that FreeBSD 6.0 is out the door, GNOME 2.12.1 has
been merged into the FreeBSD ports tree. Check out the
<a
href="http://lists.freebsd.org/pipermail/freebsd-gnome/2005-November/012608.html">
official announcement</a> for more information.
official announcement</a>
for more information.
<a href="http://www.freebsd.org/gnome/docs/faq2.html#q21">
Packages</a>
built against the update ports tree will be available
shortly.
Be sure to use the <a href="http://www.freebsd.org/gnome/gnome_upgrade.sh">upgrade
script</a> to handle the upgrade process!
</p>
shortly. Be sure to use the
<a href="http://www.freebsd.org/gnome/gnome_upgrade.sh">
upgrade script</a>
to handle the upgrade process!</p>
</event>
</day>
</month>