From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-maintainers@ecos.sourceware.org
Subject: Bugzilla upgrade to 4.2.3
Date: Tue, 23 Oct 2012 11:29:00 -0000 [thread overview]
Message-ID: <50867F7D.1050602@ecoscentric.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Hi
Just to give you advance notice that eCosCentric are in the process of
upgrading Bugzilla to the latest stable version since this will also
affect bugs.ecos.sourceware.org.
This is a major version upgrade which will necessitate bringing Bugzilla
down for the duration (which should take no more than an hour). The
upgrade should happen over the next week, time permitting, once our
internal tests of eCosCentric-specific custom modules have completed. I
will send you notification in advance shortly before and after the upgrade.
For a list of improvements please read the following release notes (we
are currently running a security patched version of Bugzilla 3.4.14):
http://www.bugzilla.org/releases/4.2.3/release-notes.html
http://www.bugzilla.org/releases/3.6.11/release-notes.html
-- Alex Schuilenburg
Managing Director/CEO
eCosCentric Limited
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4524 bytes --]
reply other threads:[~2012-10-23 11:29 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=50867F7D.1050602@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).