Closed Bug 286273 Opened 20 years ago Closed 20 years ago

Release Notes for Bugzilla 2.18.1

Categories

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

2.18
defect

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: mkanat, Assigned: mkanat)

References

()

Details

Attachments

(2 files, 2 obsolete files)

We need to modify the release notes on the 2.18.1 branch. When you do so, please remember to carry over the changes also to the tip, although you may have to do this cleverly. Hopefully the relnote keyword should help us with this.
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.18
Attached patch Release Notes for 2.18.1 (obsolete) — Splinter Review
OK, here they are. We also need to update the 2.18 Release Notes on the tip, because they apparently aren't in sync with the branch.
Assignee: general → mkanat
Attachment #178765 - Flags: review?(justdave)
Attachment #178765 - Attachment is obsolete: true
Attachment #183212 - Flags: review?(kevin.benton)
Attachment #178765 - Flags: review?(justdave)
Comment on attachment 183212 [details] [diff] [review] Release Notes with a Link to the SecAdvs Suggest adding hyperlink to the full change listing. Also, per your request, should update URL for security changes (2.16.7 currently). Wondering out loud - should "Detailed Version-To-Version Release Notes" be changed to "Detailed Version-To-Version Release Notes (pre-2.18)"? There are a number of places in the document where it still reports 2.18. Consider updating the vast majority to 2.18.1. PP 5 (L15) reports the document as preliminary. Is this still the case?
Attachment #183212 - Flags: review?(kevin.benton) → review-
(In reply to comment #3) > PP 5 (L15) reports the document as preliminary. Is this still the case? That's only on the tip, which has the wrong release notes. Only the 2.18 branch has the right release notes. I'm going to fix that when I check in these release notes. :-) All your other comments are spot-on. :-)
Attached patch v3Splinter Review
OK, this version should be complete, now.
Attachment #183212 - Attachment is obsolete: true
Attachment #183242 - Flags: review?
Comment on attachment 183242 [details] [diff] [review] v3 >+Two security issues were fixed in Bugzilla 2.18.1, neither of them >+critical. >+ >+See <A href="http://www.bugzilla.org/security/2.16.8/">http://www.bugzilla.org/security/2.16.8/</A> for details. shouldn't that be http://www.bugzilla.org/security/2.18.1/
(In reply to comment #6) > shouldn't that be http://www.bugzilla.org/security/2.18.1/ The directories are named after the earliest *affected* version. That's how they all work, for the security advisories.
Flags: blocking2.18.1?
Flags: approval2.18?
Oh, actually, this is also getting checked-in on the tip, but the patch will be slightly different. The end result will be that the branch release notes and the tip release notes will be identical. (There are not any release notes for 2.20 yet.)
Flags: approval?
Attachment #183242 - Flags: review? → review+
Flags: blocking2.18.1?
Flags: blocking2.18.1+
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
2.18: Checking in docs/rel_notes.txt; /cvsroot/mozilla/webtools/bugzilla/docs/rel_notes.txt,v <-- rel_notes.txt new revision: 1.24.2.8; previous revision: 1.24.2.7 done Tip: Checking in docs/rel_notes.txt; /cvsroot/mozilla/webtools/bugzilla/docs/rel_notes.txt,v <-- rel_notes.txt new revision: 1.30; previous revision: 1.29 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Here's the tip version of the patch -- it makes the tip relnotes identical to the 2.18 branch relnotes, when before the tip relnotes were actually *older* than the 2.18 relnotes. :-)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: