HEADS UP: GNOME 2.6 TODO list

[Adam Weinberger]

>> (03.12.2004 @ 0403 PST): Jeremy Messenger said, in 2.4K: <<
> GNOME team did the awsome job on this, so thanks! :-) I will try to test 
> many stuff and others as usually.

Heh. Where exactly do you think we'd be without you, Mezz? ;;)

> Do you still need someone to test on upgrade script or it's done?

I haven't been able to test the upgrade script in a bit because there's
a number of ports (sound-juicer, rhythmbox, etc.) that won't build
against the new gstreamer, and there's some other stuff that won't build
that I don't remember cuz I just woke up and wtf am I doing writing
emails when I only have 1 eye open.

I've been disgustingly bogged down with schoolwork, and I'm going to be
quite AFK next week, so I won't be able to test stuff for a while. More
upgrade testing would be GREAT.

Basically, I've been testing mostly upgrades when just x11/gnome2, and
when all GNOME metaports are installed. What would be really neat is to
have some upgrade tests when weird configurations of stuff are
installed. Remove parts of packages, put bizarre libraries under the gtk
dirs, install everything into a non-standard ${PREFIX} and see if the
upgrade script honours it entirely, etc.

Also, now is when considering usability is super important. We need it
to work for the n00b, but still provide lots of acronyms for the geeky.
I've made the output as simple and explanatory as possible, and just let
the actual work be shown in the logfile. I'd *love* suggestions on how
to improve the interface. Also spelling/grammar checks, and also any
suggestions for the code itself to make this script as reusable as
possible.

And you thought I was gonna say, "Nah, it's done, go play monkey-bubble." ;;)

# Adam


--
Adam Weinberger
adamw at gnome.org  \\oo//  adamw at FreeBSD.org
adamw at vectors.cx  \\// adamw at magnesium.net
http://www.vectors.cx