Bugzilla – Full Text Bug Listing
| Summary: | Upgrade to Bugzilla 4.2 | ||
|---|---|---|---|
| Product: | Community | Reporter: | Denis Roy <denis.roy> |
| Component: | Bugzilla | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | contact, eclipse, LpSolit, markus.kell.r, robert.elves, steffen.pingel, stephen.francisco |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 104100, 304229, 308533 | ||
|
Description
Denis Roy
cc'ing the usual Mylyn suspects. FWIW, I don't have a date planned, but it will definitely happen after Juno. Thanks. Let us know when the sandbox is running 4.2. Mylyn supports Bugzilla 4.2 but it would be great to do a round of testing against the Eclipse.org instance. For my own notes, while upgrading some of the perl modules, the latest DBD::mysql didn't compile. I get the feeling our .so is too old. http://search.cpan.org/CPAN/authors/id/C/CA/CAPTTOFU/DBD-mysql-4.018.tar.gz installed just fine, but it's only on bugs-vm2 I've got a sandbox running here: https://bugs.eclipse.org/bugstest It's not running mod_perl and it's using a slow database, but it does work. I haven't ported our custom template changes yet, will do so shortly. I did a quick test and the basics create and comment of existing bugs work I've scheduled the upgrade for Friday afternoon, July 27. FYI, I was on another bugzilla system that upgraded to 4.2. The change that got the most negative feedback was the switch to HTML format emails. Most users thought it was difficult to read/ugly. It's easy to go into preferences and turn it back to plain text, but it would have been less disruptive if the 'default' was non-html. I don't know if you have control over that or would just want to inform everyone of how to turn it off if they hate the html emails. Thanks for the feedback. The HTML mail format is what scares me the most. I've done some work towards polishing it up, but it remains just an odd format to present data we're used to seeing in plain text. I could completely suppress the HTML email, or I could probably mass-change everyone's preference to prefer plaintext email (and those who wish HTML could choose so). The other issue that's bothering me is this decision from the Mozilla team to postpone 4.2 deployment on Mozilla's production Bugzilla instance. https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/BIJgdHYR-5I Since the issues haven't been disclosed, it's hard to judge the severity or predict their impact on bugs.eclipse.org. But by the same token, upgrading to 4.2 here could provide the Mozilla team some valuable, constructive feedback. The upgrade from 4.0.x to 4.2.x cannot be reversed without data loss, however. (In reply to comment #7) > I don't know if you have control over that or would > just want to inform everyone of how to turn it off if they hate the html > emails. As for all user preferences, admins can set the default value to "text only", so only those who want HTML emails will have to change their preferences. So this is not an issue. (In reply to comment #8) > The other issue that's bothering me is this decision from the Mozilla team to > postpone 4.2 deployment on Mozilla's production Bugzilla instance. The reasons to postpone the bmo upgrade aren't secret. The main reason is that some changes in Search.pm prevent some old queries from returning the expected results, see e.g. the discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=677757. Some other reasons have to do with some local customizations and so aren't relevant to Eclipse's Bugzilla. Just in case, the meta-bug about the upgrade is https://bugzilla.mozilla.org/show_bug.cgi?id=764897. Note that you shouldn't worry too much about bmo not upgrading to 4.2.1 yet. Some other major installations, such as RedHat, Gentoo, KDE and Apache, are already running Bugzilla 4.2.1 successfully, see http://lpsolit.wordpress.com/bugzilla-usage-worldwide/. And the reason that we lag so much to release 4.2.2 is because 4.2.1 is pretty stable and no new release is required for now. ;) Thanks for confirming. I'll proceed with the upgrade as planned. (In reply to comment #10) > Thanks for confirming. I'll proceed with the upgrade as planned. Please postpone the upgrade or first read what I will write in a recently discovered security bug on bmo. I will CC Denis to that security bug so that he has all the details and can make the final decision. > Please postpone the upgrade or first read what I will write in a recently
> discovered security bug on bmo.
Thanks for the head's up. I'll upgrade as planned and I'll use the plaintext workaround you proposed on b.m.o.
Bugzilla was upgraded to 4.2.1. If you see anything missing or broken, please open separate bugs so they can be addressed. |