On Tue, 2006-02-07 at 10:25 -0700, Elijah Newren wrote: > On 2/7/06, Calum Benson <[EMAIL PROTECTED]> wrote: > > > Uh, we're just over a week *past* UI freeze. ;-) > > > > I know, but didn't we always do UI reviews after the freeze, with > > s/the freeze/a freeze/ > > > maintainers having special release team dispensation to change stuff > > after that that the UI review recommended? > > Yes, but didn't we used to have a soft UI freeze + a hard UI freeze, > with the UI review coming in between? (e.g. see > http://www.gnome.org/start/2.5/). We're almost to the time of what > would have been the hard UI freeze in such a schedule. > > Anyway, I think it'd make sense to probably approve stuff that was > changed in response to UI review recommendation, if done soon, but > given that it is later in the release cycle we do need to weigh it > against possible work caused to the documentation or release notes > writers as well as possibility for instability if the changes are not > small. So, I'd probably lean towards approving such stuff, but I > think it's too late to give blanket approval to changes made in > response to UI review at this point.
Ok, well... what I'd suggest then is that we[1] maybe try and do a UI review of the components whose maintainers have expressed an interest in being reviewed (or who express such an interest in the next day or two), and just seek approval for those changes. And then do it properly again next time :) Cheeri, Calum. [1] Or possibly just me, if nobody else is particularly interested... -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED] Java Desktop System Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
