Closed Bug 92818 Opened 24 years ago Closed 24 years ago

CHANGES file is hopelessly outdated

Categories

(Bugzilla :: Bugzilla-General, defect, P1)

x86
Linux
defect

Tracking

()

RESOLVED FIXED
Bugzilla 2.14

People

(Reporter: myk, Assigned: barnboy)

Details

The "CHANGES" file in the Bugzilla distribution has not been updated since 1999. It should either be deleted or be redone with links to whereever it is we store this information nowadays (just like we updated the README file last milestone).
This file needs to stay in the archive for people upgrading from versions 2.6 and older. They need to do everything listed in this file before they run checksetup.pl for the first time, because checksetup.pl didn't exist yet at that time. However, if it's not clear already, it should be made clear that's the purpose of the file, and it should be mentioned in the readme....
Assignee: justdave → barnboy
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.14
I will add something about this into the release notes. We need to rename this file to something like "CHANGES-pre-2.8". Let's make sure we have this right though. 2.10 was the first version that had checksetup.pl? In other words, anyone upgrading from 2.8 or later is covered by checksetup.pl? And you only have to make changes before checksetup.pl if you're running 2.6 or earlier?
I *believe* (not positive) that thanks to the efforts of some other people upgrading, that checksetup.pl will upgrade anything from version 2.5 onwards. It was not in the distribution until 2.10, but has had changes made to it since then to allow it to upgrade earlier versions. I'm pretty sure 2.5 is the earliest version it supports. I would probably leave the "pre-2.8" designation on the file anyway, just to play it safe.
Status: NEW → ASSIGNED
Changed name to "UPGRADING-pre-2.8".
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.