Re: Shell vs. Menus for 2.18



Vincent Untz wrote:
Le mardi 13 février 2007, à 13:06, Thomas Wood a écrit :
Rodrigo Moya wrote:
On Tue, 2007-02-13 at 10:51 +0000, Thomas Wood wrote:
Rodrigo Moya wrote:
On Fri, 2007-02-09 at 22:22 +0000, Thomas Wood wrote:
[...]
as talked on #control-center, I am ok with reverting to the old menu,
but let's try to come up with fixes for the issues, and if we can't,
let's revert before the final 2.18.0, ok?
How close are we going to wait before making a decision? With 2.17.91 out, we still have these accessibility and usability problems. As Rodney said last night, the whole flow mechanism for tiles in libslab needs to basically be re-worked. Can we really do this while we are supposed to be nearing hard code freeze?

I was thinking about waiting until the hard code freeze, which is March
5th. That gives us a few weeks to come up with solutions for all the
problems (or at least the most important ones). When we get to the hard
code freeze, if they are not solved, we revert back. Does this sound ok?
Ideally we need some input from the release team here. Adding to CC...

While it's possible to wait for hard code freeze to take such a
decision, it'll be too late to update the doc, the release notes, etc.

Deciding now is really better.

With this in mind them, I'm going to ask the release team for approval on reverting the menu system back to the way it was in 2.18.

I think taking the risk that all the bugs in libslab/shell will be fixed before hard code freeze is too great. However, people will still get the chance to switch to the new shell by using editing their menus via alacarte.

So release team, do we have your approval to revert the changes to the System menu, back to the way they were in 2.18?

Regards,

Thomas



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