Re: Branching GConf


I mailed a design for the new features to gconf-list (dated
October 23rd); there's been some minor tweaking but no
substantial changes.

If you'd like to have input or you have identified some requirements
for GConf in GNOME 2.0, now is the time to send them (to gconf-list gnome org).

As I expect many GNOME maintainers are looking at ways to use GConf,
this is also a good time to start looking at adoption and migration
issues (if you're not already using GConf).


>Delivered-To: gnome-private-members gnome org
>Delivered-To: gnome-hackers gnome org
>X-Authentication-Warning: hp set sender to hp redhat com 
using -f
>To: gnome-hackers gnome org, gconf-list gnome org, 
nautilus-list lists eazel com, gnome-i18n gnome org
>Subject: Branching GConf
>From: Havoc Pennington <hp redhat com>
>User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
>MIME-Version: 1.0
>X-BeenThere: gnome-hackers gnome org
>X-Loop: gnome-hackers gnome org
>X-Mailman-Version: 2.0beta5
>List-Id: <>
>X-BeenThere: gnome-private-members gnome org
>X-Loop: gnome-private-members gnome org
>Colm has time to start working on some new features for GConf 2, so
>I'm branching the stable version to gconf-1-0. The gconf-1-0 branch is
>the one that's going to end up in GNOME 1.4. 
>All bugfixes and such should go in both branches; unstable breakage
>will go in HEAD. Will probably port HEAD to GLib 1.3.x in a while, but
>not right away, I'd like to get closer to the 1.4 release before
>making the diff between branches that large.
>Nautilus tinderbox and build instructions should move to recommending
>the gconf-1-0 branch.
>gnome-hackers mailing list
>gnome-hackers gnome org

gnome-hackers mailing list
gnome-hackers gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]