View source for BMO/42Upgrade/Alpha

  Things to do before sending this out to the public:
  * update 4.2 bugmail (pending review)
  * sanitise database (need to file a bug)
  * allow smtp delivery outside mozilla.org (enable limitedemail ext, switch to sendmail for delivery, file bug asking  for flows to be updated)
  * Speak with security team to determine if security review of bugzilla 4.2 is needed.

Subject: Mozilla Bugzilla 4.2 Upgrade Testing Announcement - June 25th, 2012

Greetings,

The Mozilla Bugzilla team is happy to announce the first test release of the next version of Bugzilla based on the upstream 4.2 code base.

We are aiming to have the upgrade completed by July 23rd, 2012. Please let us know if that date will have any negative impact on development schedules.

For more detailed project information as well as the full schedule, see:
https://wiki.mozilla.org/BMO/42Upgrade

Please test drive at:
https://bugzilla.allizom.org

The main area of focus for our test releases are stability. Functionality that currently works in our 4.0 code base should continue to work as expected in the new version 4.2. Please let us know of any customizations that are missing or not working properly.

Please feel free to point your various scripts and third party applications that use the XMLRPC/JSON API at the test server to make sure they continue to function properly. Also a test instance of the BzAPI is available for testing your tools that need it ([https://bugzilla.mozilla.org/767583 bug 767583]).

There are also numerous new features/fixes that are part of the upstream version 4.2. Some more notable updates include enhanced WebService support, UI enhancements, HTML email, and search improvements. For more detailed information on what has changed since the last upstream release, check out the full release notes page at http://www.bugzilla.org/releases/4.2/release-notes.html

Note: The code on the backend supporting search has changed significantly from 4.0 and special attention should be given to verify your saved searches still produce the expected results. As part of the sanitization process of the data for testing, saved searches are removed from the database. This is in case there is any sensitive data contained in the searches that someone may see when requesting a copy of the database.

As a workaround to test your saved searches on the 4.2 system:

1. Go to https://bugzilla.mozilla.org.
2. Run your saved search as you normally would which pulls up the
complete bug list.
3. Click 'Edit Search' at the bottom of the buglist page.
4. When on the query builder page, change the hostname in the address field from bugzilla.mozilla.org to bugzilla.allizom.org and reload the
query page.
5. Click 'Search' which will bring up a new bug list.
6. You should get similar results in both places although private bugs will be absent on the 4.2 test system.

The database is a recent, sanitized snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Being that is it sanitized, private bugs, products, groups, etc. will not be present.

Note: Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order of the UI. We can however enable email delivery to specific email addresses on request to test the new email features of Bugzilla.

We are asking for everyone to get involved as much as possible with testing and feedback on all of the test releases to help us make this the most robust and stable roll out as possible.

Please file any bug reports in the production Bugzilla system at https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&version=Development%2FStaging

Thanks, The Mozilla Bugzilla Team
https://wiki.mozilla.org/BMO