159790 - (bz-2.18-release) 2.18 Release Tracking Bug

Status: RESOLVED FIXED

(Bugzilla :: Bugzilla-General, defect)

Description

[Gervase Markham [:gerv]]

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

Don't add any dependencies other than that of guaranteed permanent dependencies
by definition (which is probably the 2.18 release notes and nothing else).

Comment 1

[Max Kanat-Alexander]

Attachment: Set the Bugzilla Version to 2.18 :-)

Man, I just wanted to write the patch. :-)

Comment 2

[Max Kanat-Alexander]

Attachment: Um, Correctly Set the Version

Arrggh. :-) Jake pointed out that I also have to set the version in the Docs.
:-)

Just change the FIXME part on the day that we actually release.

Comment 3

[Shane H. W. Travis]

It seems to me that bz-nextver should be 2.20 and not 2.18.1.

The only place this is used is in faq.xml, and the context is as follows:

Q: What bugs are in Bugzilla right now?
...
You can view bugs marked for &bz-nextver; release
<ulink url="http://bugzilla.mozilla.org/buglist.cgi?
product=Bugzilla&amp;target_milestone=Bugzilla+&bz-nextver;">here</ulink>.
This list includes bugs for the &bz-nextver; release that have already
been fixed and checked into CVS.
...

It could make sense either way, really. Jake or Gerv, you want to speak up on 
the original intent/future intent of this?

Comment 4

[Gervase Markham [:gerv]]

bz-nextver, if we keep it rather than ripping it out, should be 2.20.

Gerv

Comment 5

[Jacob Steenhagen]

(In reply to comment #3)
> It seems to me that bz-nextver should be 2.20 and not 2.18.1.

You are correct, it is intended to be the next major stable release (eg, what
the current devel version is stiving to be).

Comment 6

[Max Kanat-Alexander]

OK, 2.18 is ready when you are, justdave.

Order of things to be done:

1) Check-in bug 276237 and bug 277621 (2.18 patches).
2) Check-in bug 150149 (2.18 Release Notes).
3) Check-in bug 278298 (2.16.8 Release Notes).
4) Check-in the patch on this bug (version numbering stuff).
5) Do version-numbering stuff for 2.16.8 and 2.19.2.

6) Create tarballs, do everything that's part of the release checklist before 
   the announcement.

7) Check-in bug 278303 (Security Advisory).
8) Check-in bug 278294 (2.16.8 Release Page).
9) Check-in bug 277510 (Changes page, all releases).
10) Check-in bug 277615 (New Features page for 2.18)
11) Check-in bug 277511 (Download page)
12) Check-in bug 277509 (Status Update)
13) Check-in bug 277512 (News Update)

14) Send announcement from bug 277515, do all the things post-announcement.

Comment 7

[Dave Miller [:justdave]]

version changes committed

Checking in Bugzilla/Config.pm;
new revision: 1.21.2.3; previous revision: 1.21.2.2
Checking in docs/xml/Bugzilla-Guide.xml;
new revision: 1.37.2.9; previous revision: 1.37.2.8

(and yes, I fixed the FIXME on the date) :)

I'll come back and resolve the bug once the website is staged.

BUGZILLA-2_18 cvs tag has been set.

Comment 8

[Max Kanat-Alexander]

OK. And you fixed the bz-netver thing, too, right? (It should have been 2.20.)

Comment 9

[Dave Miller [:justdave]]

whoop! whoop!