gio/gvfs vs. hardcode freeze.



i propose to not include gio/gvfs for hardcode freeze on monday to
hopefully get in some more fixes (if they do not include string
changes) and regressions like
http://bugzilla.gnome.org/show_bug.cgi?id=517632 (nobody working on it
afaik) or http://bugzilla.gnome.org/show_bug.cgi?id=509620 (ftp support,
Company is on it).
perhaps giving them a few more days makes sense, like "hardcode freeze
on thursday for gio/gvfs/nautilus and (as before) on monday for all
other modules". it would also be another signal from the r-t that we
definitely back them in their efforts to get it done.
if we agreed on this we should tell alex and the hackers in #nautilus
about.

not sure if my idea makes sense, comments?

andre
-- 
 mailto:ak-47 gmx net | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil



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