Last Comment Bug 503055 - (bmo-upgrade-34) Upgrade b.m.o to 3.4
: Upgrade b.m.o to 3.4
11/15/2009 @ 6pm PST
Classification: Other
Component: General (show other bugs)
: other
: All All
-- enhancement (vote)
: ---
Assigned To: Dave Miller [:justdave] (
: 506748 (view as bug list)
Depends on: 438362 453436 495989 507483 515214 518073 518517 518518 521959 523325 523455 528805
Blocks: 506825
  Show dependency treegraph
Reported: 2009-07-08 04:12 PDT by Frédéric Buclin
Modified: 2011-06-26 22:59 PDT (History)
14 users (show)
See Also:
Due Date:
QA Whiteboard:
Iteration: ---
Points: ---

Mockup of possible bugzilla redesign (132.08 KB, image/png)
2009-10-26 12:14 PDT, Jennifer Morrow [:Boriss] (UX)
no flags Details

Description User image Frédéric Buclin 2009-07-08 04:12:57 PDT
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. ;)
Comment 1 User image Frédéric Buclin 2009-07-27 14:16:37 PDT
*** Bug 506748 has been marked as a duplicate of this bug. ***
Comment 2 User image Jennifer Morrow [:Boriss] (UX) 2009-10-26 12:14:58 PDT
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.
Comment 3 User image Reed Loden [:reed] (use needinfo?) 2009-10-26 13:07:37 PDT
(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

We should probably split this off into a new bug.
Comment 4 User image Max Kanat-Alexander 2009-10-26 14:10:52 PDT
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 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.
Comment 5 User image Dave Miller [:justdave] ( 2009-10-26 19:00:46 PDT
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.
Comment 6 User image Dave Miller [:justdave] ( 2009-10-29 11:15:10 PDT
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.
Comment 7 User image Dave Miller [:justdave] ( 2009-11-14 21:19:51 PST
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)
Comment 8 User image Dave Miller [:justdave] ( 2009-11-22 10:14:03 PST
This was done.  Followup issues are being dealt with on bug 528846.

Note You need to log in before you can comment on or make changes to this bug.