Bugzilla 3.4rc1 will be released in the coming hours. We should upgrade b.m.o to 3.4rc1 once it's available to 1) catch remaining bugs and perf issues before we release 3.4 final next month, and 2) benefit from new features. ;)
*** Bug 506748 has been marked as a duplicate of this bug. ***
Created attachment 408430 [details]
Mockup of possible bugzilla redesign
I'm attaching a mockup of a possible Bugzilla redesign I did awhile ago. I was thinking about how to direct new users to the most common actions (e.g. reporting a bug) while not getting in the way of experienced users. It's true that the large buttons of the currently proposed design easily direct people to the most common tasks, but it seems a bit like overkill at best and patronizing at worst. I think we can find ways to direct the users' focus to the main paths in ways other than size.
I imagined something like the attachment would be a kind of intro/start screen, and the style of the other pages (e.g. bugs themselves) would be more minimal and fast loading, but with a similar visual style.
(In reply to comment #2)
> Created an attachment (id=408430) [details]
> Mockup of possible bugzilla redesign
Yeah, Ryan made this into a real template available at http://github.com/ryandoherty/Bugzilla-redesign.
We should probably split this off into a new bug.
Although I'm not working on the upgrade, I wanted to make a comment--if that date in the Status Whiteboard is the date that the upgrade will happen, then based on feedback received from Engineering during the 3.2 upgrade, I would strongly recommend that an announcehtml header pointing to the stage installation be put up on the current bugzilla.mozilla.org--one that includes a message that this is a major upgrade that will feature UI changes. After the last upgrade, it was communicated to me and the other Bugzilla developers and administrators that engineers did not have sufficient warning that the upgrade would be significant and change the UI.
The announcement won't go up there until all of the changes that need to be made to it before it can go live have been made, and that hasn't happened yet. Personally I'm skeptical of being able to maintain that date, but that's still what we're aiming for at the moment. If I don't get the blocker list cleared by tomorrow it's probably going to get pushed off, because I want a few days of everyone being able to see what they're going to get before it gets there.
No way this is happening tonight, don't have the final product in place on the staging site yet, and it needs a few days of testing once that's done.
preliminary security audit passed, we have an official go for upgrading tomorrow afternoon. :) (as evident by the downtime notice already in the banner from a few hours ago)
This was done. Followup issues are being dealt with on bug 528846.