Closed Bug 286271 Opened 17 years ago Closed 17 years ago

Release Bugzilla 2.18.1, 2.19.3, and 2.16.9

Categories

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

2.19.2
defect

Tracking

()

RESOLVED FIXED
Bugzilla 2.16

People

(Reporter: mkanat, Assigned: mkanat)

References

(Blocks 1 open bug)

Details

This bug tracks the release of 2.18.1  Comment on any general issues to do with
the 2.18.1 release here.

Don't add any dependencies other than that of guaranteed permanent dependencies
by definition. In this case, that means web site updates and the 2.18.1 release
notes only.
Summary: Release 2.18.1 → Release Bugzilla 2.18.1
Flags: blocking2.18.1?
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.18
Version: 2.19.2 → 2.18
OK, actually, let's make this the tracking bug for both of them, since the
release will be simultaneous.

2.19.3 will need a large "Hazardous" sticker placed upon it, as we ourselves are
not even done with the regression-finding.
Summary: Release Bugzilla 2.18.1 → Release Bugzilla 2.18.1 and 2.19.3
Target Milestone: Bugzilla 2.18 → ---
Version: 2.18 → 2.19.2
Depends on: 286273
Depends on: 286274
Depends on: 286275
Depends on: 286276
Depends on: 286277
Depends on: 286278
Depends on: 286281
Flags: blocking2.18.1? → blocking2.18.1+
Target Milestone: --- → Bugzilla 2.18
Blocks: 287544
No longer blocks: 287544
Depends on: 287544
No longer depends on: 286274
No longer depends on: 286278
Depends on: 290249
We will also need 2.16.9, because we have a minor security patch for it.
Summary: Release Bugzilla 2.18.1 and 2.19.3 → Release Bugzilla 2.18.1, 2.19.3, and 2.16.9
Status: NEW → ASSIGNED
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
Depends on: 293690
We plan to do this release today. I have a staged website, but it has the
security advisory posted on it, so I don't want to link to it yet from a public
Bugzilla.

I'm almost through the release process, all blockers are awaiting approval,
things are looking good.
Upped versions:

Tip:

Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v  <--  Config.pm
new revision: 1.40; previous revision: 1.39
done

2.18:

Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v  <--  Config.pm
new revision: 1.21.2.4; previous revision: 1.21.2.3
done

2.16:

Checking in globals.pl;
/cvsroot/mozilla/webtools/bugzilla/globals.pl,v  <--  globals.pl
new revision: 1.169.2.27; previous revision: 1.169.2.26
done
Created tags:

cvs tag -FR -rBUGZILLA-2_18-BRANCH BUGZILLA-2_18_1
cvs tag -FR -rBUGZILLA-2_18_1 BUGZILLA-2_18-STABLE
cvs tag -FR -rBUGZILLA-2_18-STABLE Bugzilla_Stable

cvs tag -FR -rBUGZILLA-2_16-BRANCH BUGZILLA-2_16_9
cvs tag -FR -rBUGZILLA-2_16_9 BUGZILLA-2_16-STABLE

cvs tag -FR BUGZILLA-2_19_3
OK, tarballs have been pushed to stage.
OK, new web site checked-in:

Checking in index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/index.html.tmpl,v  <--  index.html.tmpl
new revision: 1.15; previous revision: 1.14
done
Checking in download/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/download/index.html.tmpl,v  <-- 
index.html.tmpl
new revision: 1.19; previous revision: 1.18
done
Checking in news/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/news/index.html.tmpl,v  <-- 
index.html.tmplnew revision: 1.16; previous revision: 1.15
done
Checking in releases/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/index.html.tmpl,v  <-- 
index.html.tmpl
new revision: 1.8; previous revision: 1.7
done
RCS file:
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.16.9/index.html.tmpl,v
done
Checking in releases/2.16.9/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.16.9/index.html.tmpl,v 
<--  index.html.tmpl
initial revision: 1.1
done
RCS file:
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.16.9/release-notes.html.tmpl,v
done
Checking in releases/2.16.9/release-notes.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.16.9/release-notes.html.tmpl,v
 <--  release-notes.html.tmpl
initial revision: 1.1
done
RCS file:
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.18.1/index.html.tmpl,v
done
Checking in releases/2.18.1/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.18.1/index.html.tmpl,v 
<--  index.html.tmpl
initial revision: 1.1
done
RCS file:
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.18.1/release-notes.html.tmpl,v
done
Checking in releases/2.18.1/release-notes.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.18.1/release-notes.html.tmpl,v
 <--  release-notes.html.tmpl
initial revision: 1.1
done
Checking in security/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/security/index.html.tmpl,v  <-- 
index.html.tmpl
new revision: 1.7; previous revision: 1.6
done
RCS file:
/cvsroot/mozilla-org/html/projects/bugzilla/security/2.16.8/index.html.tmpl,v
done
Checking in security/2.16.8/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/security/2.16.8/index.html.tmpl,v 
<--  index.html.tmpl
initial revision: 1.1
done
RCS file: /cvsroot/mozilla-org/html/projects/bugzilla/status/2005-05-11.html.tmpl,v
done
Checking in status/2005-05-11.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/status/2005-05-11.html.tmpl,v  <-- 
2005-05-11.html.tmpl
initial revision: 1.1
done
Checking in status/changes.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/status/changes.html.tmpl,v  <-- 
changes.html.tmpl
new revision: 1.7; previous revision: 1.6
done
Checking in status/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/status/index.html.tmpl,v  <-- 
index.html.tmpl
new revision: 1.8; previous revision: 1.7
done
Published as part of bug 286269.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Oops, wrong bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
OK, secadv sent, release announcement sent, and all the version trackers have
been updated. Well, except MacUpdate -- we're going to work on that.

But this is DONE. :-)
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.