From: Christian Ruppert <idl0r@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Bugzilla maintenance
Date: Thu, 23 May 2013 23:51:33 +0200 [thread overview]
Message-ID: <20130523215132.GA4771@odin.qasl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
Hey,
I just wanted to let you all know that our Bugzilla (bugs.gentoo.org) will be
down for maintenance on Sat. May 25. The maintenance window will begin around
04:00 PM UTC until 04:45 PM UTC.
This maintenance will include an update to Bugzilla 4.4. Here are some release
highlights:
It is now possible to add yourself to the CC list when uploading an attachment
and when editing an existing one.
When reporting a new bug, flags which are not available for the selected
component and those which the reporter cannot edit are now hidden instead of
being disabled. For existing bugs, unset flags are also hidden by default.
Clicking the (set flags) or (more flags) link will make them appear.
When viewing a bug, the list of duplicated bugs is now listed near the top of
the page.
The See Also field now supports URLs pointing to GitHub by default. If the new
MoreBugUrl extension included in this release is enabled, then you can also add
URLs pointing to: bugs.php.net, RT, appspot.com (Rietveld), Review Board, and
getsatisfaction.com.
There is a new user preference to not prepend "New:" to the subject of bugmails
when reporting a new bug. Some email clients couldn't thread emails correctly
due to this.
There is a new email event to get notifications when the product or component of
a bug changes.
All bugmails now have a X-Bugzilla-Flags email header, listing currently set
flags.
The update should also fix:
https://bugs.gentoo.org/335754
https://bugs.gentoo.org/366161
and
https://bugs.gentoo.org/431840
When: Sat. May 25
Start: 04:00 PM UTC
Estimated duration: 45 minutes
Affected services: bugs.gentoo.org
Our Bugzilla will *not* be available during the update. Any other services are
not affected.
--
Regards,
Christian Ruppert
Gentoo Linux developer, Bugzilla administrator and Infrastructure member
Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2013-05-23 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130523215132.GA4771@odin.qasl.de \
--to=idl0r@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox