public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: John Dallaway <jld@ecoscentric.com>,
	  ecos-maintainers@ecos.sourceware.org
Cc: support@ecoscentric.com
Subject: [Fwd: Release of Bugzilla 2.18.6, 2.20.3, 2.22.1, and 2.23.3]
Date: Sun, 15 Oct 2006 22:31:00 -0000	[thread overview]
Message-ID: <4532B6A5.4060403@ecoscentric.com> (raw)

Dudes

I have just made the upgrade to 2.18.6 - it went relatively smoothly.

However, as per this email, 2.18.x will be end-of-life'd when 3.0
finally comes out.  When this happens, eCosCentric will upgrade to
Bugzilla 3.0 rather than 2.20.x or 2.22.x as we are looking to use some
of the new features that will be available in 3.0.  There will be ample
warning when this happens as it is likely there will need to be some
downtime, so consider this advance warning :-)

-- Alex



-------- Original Message --------
Subject: Release of Bugzilla 2.18.6, 2.20.3, 2.22.1, and 2.23.3
Date: Sun, 15 Oct 2006 03:09:10 -0700
From: Max Kanat-Alexander <mkanat@bugzilla.org>
Organisation: Bugzilla Project
To: announce@bugzilla.org

  We have many releases for you, today!

  Bugzilla 2.18.6 and 2.20.3 are security-fix releases for our older
branches.

  Bugzilla 2.22.1 is our first bugfix release in the 2.22 series,
and contains many useful fixes that improve the experience of using
Bugzilla.

  Finally, we are releasing an unstable development snapshot, Bugzilla
2.23.3. This snapshot has both custom fields and mod_perl support,
but has not been tested as thoroughly as our other releases. The 2.23
series will eventually culminate in Bugzilla 3.0.

  Users of the 2.18.x series should note that 2.18.x will reach
End Of Life when Bugzilla 3.0 is released. There are more details
in our Status Update.

  We hope you enjoy all our new releases!


Download
--------
Bugzilla is available at:

http://www.bugzilla.org/download/


Release Notes & Changes
-----------------------
Before installing or upgrading, it is VERY IMPORTANT to read
the Release Notes:

2.18.6: http://www.bugzilla.org/releases/2.18.6/release-notes.html
2.20.3: http://www.bugzilla.org/releases/2.20.3/release-notes.html
2.22.1: http://www.bugzilla.org/releases/2.22.1/release-notes.html

To see a list of all changes between your version of Bugzilla and
the current version of Bugzilla, you can use the chart at:

http://www.bugzilla.org/status/changes.html


Security Advisory
-----------------
All of our releases contain important security fixes. Read about
them here:

http://www.bugzilla.org/security/2.18.5/


Status Update
-------------
To see what's new with the Bugzilla Project, including all the features
of our latest Development Release, see our latest Status Update:

http://www.bugzilla.org/status/2006-10-15.html


Try Out Bugzilla
----------------
If you'd like to test-drive Bugzilla, you can use the demo
installations of Bugzilla at:

http://landfill.bugzilla.org/


Support
-------
You can ask questions for free on the mailing lists (or in IRC)
about Bugzilla, or you can hire a paid consultant to help you out:

Free Support: http://www.bugzilla.org/support/
Paid Support: http://www.bugzilla.org/support/consulting.html


About Bugzilla
--------------
Bugzilla is a "Defect Tracking System" or "Bug-Tracking System."
Defect Tracking Systems allow individual or groups of developers
to keep track of outstanding bugs in their product effectively.
Most commercial defect-tracking software vendors charge enormous
licensing fees. Despite being "free", Bugzilla has many features
its expensive counterparts lack. Consequently, Bugzilla has quickly
become a favorite of hundreds of organizations across the globe, and
is widely regarded as one of the top defect-tracking systems available.

See http://www.bugzilla.org/about/ for more details.

-Max Kanat-Alexander
Release Manager, Bugzilla Project


                 reply	other threads:[~2006-10-15 22:31 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=4532B6A5.4060403@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jld@ecoscentric.com \
    --cc=support@ecoscentric.com \
    /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).