Closed Bug 346501 Opened 18 years ago Closed 18 years ago

Release Bugzilla 2.18.6, 2.20.3, 2.22.1, and 2.23.3

Categories

(Bugzilla :: Bugzilla-General, defect)

Product:
Bugzilla
Component:
Bugzilla-General
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: spam, Assigned: mkanat)

References

(Blocks 1 open bug)

Details

Depends on: 346524
Depends on: 346525
No longer depends on: 346524
Depends on: 334001, 337151
Depends on: 356677
Okay, I'm starting the release process now.
Status: NEW → ASSIGNED
Okay, I've bumped the version number on all the branches, and also fixed the docs version number.
Okay, we're ready to go! I'm going to do the tags, roll the tarballs and get everything set.
All the tarballs are posted. I just have to fix all the FIXMEs on the staging site, now.
I committed all the web site changes.
Okay, I've sent the release announcements and the security advisory. I bumped all the version numbers to their "+" versions. I'll finish up with the FreshMeat stuff tomorrow--right now I really need to sleep.
2.23.2 installations are now automatically notified about the new 2.23.3 release.
Should this bug not be fixed since they have been released?
probably, yes. :)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
I just did the FreshMeat stuff now. :-) That's why the bug was still open. :-) But it's okay that it was closed, too, since it's true that the releases themselves were done.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.