[ANN] Bugzilla 2.14.5 Released
David Miller
2.14.5 is the latest release on the 2.14 branch and fixes two security bugs
in Bugzilla 2.14.4. For more detailed information, review the latest
Bugzilla status report available at
http://www.bugzilla.org/status_reports/2002-09-22.html .
The Bugzilla team strongly recommends all 2.14.x users upgrade at least to
2.14.5, if not 2.16.2, due to the security bugs fixed in this release.
All 2.14.x users who haven't already should begin planning an upgrade path
to the 2.16 branch (currently at 2.16.2, also released today). The Bugzilla
team has decided to focus development attention on newer, more maintainable
release lineages. As such, the Bugzilla team has terminated support of the
2.14 branch as of this release.
For details on upgrade options and to download 2.14.5, please see:
http://www.bugzilla.org/download.html .
Be sure to read the 2.14.5 release notes located within the release package
in docs/rel_notes.txt.
Finally, thanks to everyone who worked on this release!
--
Dave Miller Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/ http://www.bugzilla.org/
Nick Barnes
> The Bugzilla Team is pleased to announce the release of Bugzilla 2.14.5.
>
> 2.14.5 is the latest release on the 2.14 branch and fixes two security bugs
> in Bugzilla 2.14.4. For more detailed information, review the latest
> Bugzilla status report available at
> http://www.bugzilla.org/status_reports/2002-09-22.html .
>
> The Bugzilla team strongly recommends all 2.14.x users upgrade at least to
> 2.14.5, if not 2.16.2, due to the security bugs fixed in this release.
What's the current advice for Windows users?
Nick Barnes
P4DTI Project
Ravenbrook Limited
Dave Miller
Go ahead and get 2.14.5 for now, if you're still running 2.14.x on Windows.
Bugzilla was never intended to run on Windows, and although we do intend to
make it able to run on Windows in the near future, it has always in the
past required lots of hacking to run on Windows, so the work required to
install 2.16.2 won't be much worse than it was to install 2.12 or 2.14 when
they first put it in. That's one of the dangers of installing software on
a platform it's not supported on.
Hopefully it'll be much less work for them to install 2.18 (or one of the
2.17's in the near future). It would make me very happy if we could have a
2.17.4 that ran out of the box on Windows. The one bug that makes 2.16
worse than 2.14 for the amount of hacking required is the mail processing
(http://bugzilla.mozilla.org/show_bug.cgi?id=84876). Hopefully there won't
be any more security bugs, but just to be safe, we need to make that bug a
priority in the short term so Windows users have somewhere to go.
J. Paul Reed
> What's the current advice for Windows users?
I'll chime in here, since 84876 is mine.
As I noted in a comment on that bug today, 84876 is part of a bigger
rearchitecting of the Bugzilla email notifications module. It's been
postponed until bug 124174, which is also critical for running on Win32,
goes in.
If you want to see the status of bugs that affect Bugzilla's ability to
run on Win32, query on the status whiteboard field for the string
[needed for Win32bz].
Later,
Paul
-----------------------------------------------------------------------
J. Paul Reed pr...@sigkill.com || web.sigkill.com/preed
To hold on to sanity too tight is insane. -- Nick Falzone, Pushing Tin
Stephen F Roberts
>Nick Barnes wrote:
>
>>What's the current advice for Windows users?
>
>I'll chime in here, since 84876 is mine.
>
>As I noted in a comment on that bug today, 84876 is part of a bigger
>rearchitecting of the Bugzilla email notifications module. It's been
>postponed until bug 124174, which is also critical for running on Win32,
>goes in.
>
>If you want to see the status of bugs that affect Bugzilla's ability to
>run on Win32, query on the status whiteboard field for the string [needed
>for Win32bz].
...Woohoo! I had been off and on trying to find what bug was cropping up
with Windows (suppose if I actually spent time looking, I would have found
it eventually :-)
Anyway, we're currently on 2.14.4 (NT (soon 2k), apache, mysql,
ntsendmail). I had been hoping to bring down 2.17.* and mess with it. I
would like to help out bringing the code back to working (somewhat) with
Windows. The hacks to get 2.14 going on windows weren't that bad, really.
sigh... dreaming of the day I can get them to go opensource... :-/