77548 - 2.14 Release Tracking Bug

Status: RESOLVED FIXED

(Bugzilla :: Bugzilla-General, defect)

Description

[Matthew Tuck [:CodeMachine]]

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

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

Comment 1

[Dave Miller [:justdave]]

Status update:  15 bugs left
  3 need perl code.
  9 need sgml. (docs)
  1 tracking bug (covers one of the perl code bugs)
  1 release notes
  this one.

The count will go down quick when the docs show up. :-)  I just sent barnboy a 
friendly reminder.

Things to do when we release:

 1 - verify everything is final and close the tree.  No more last-minute fixemups 
after the tarball is posted! :-)
 2 - bump version number in globals.pl and check it in.
 3 - set cvs tags:
     a- cvs tag -FR BUGZILLA-2_14
     b- cvs tag -FR -rBUGZILLA-2_14 Bugzilla_Stable
 4 - make tarball:
     a- cvs checkout *** FROM [e-mail] ***
     b- cvs update -P to nuke the extra directories
 5 - repeat step 1 one more time just to be sure
 6 - upload tarball to ftp-staging
 7 - upload release notes to www.moz.org/projects/bugzilla and make any fixups
     needed to the web page
 8 - sumbit news item to www.moz.org
 9 - post announcement to netscape.public.mozilla.webtools

Should we post to bugtraq?  Since we fixed a bunch of security holes (bugzilla 
data security, not system security) not sure if we should make another security 
advisory...

Comment 2

[Dave Miller [:justdave]]

mine

Comment 3

[Jacob Steenhagen]

10 - Update http://freshmeat.net/projects/bugzilla/

Comment 4

[Matthew Tuck [:CodeMachine]]

11 - Bump to 2.15.

Comment 5

[Matthew Tuck [:CodeMachine]]

And let's not forget the security advisory, for the third version in a row
(yay!)

Comment 6

[Matthew Tuck [:CodeMachine]]

And make sure you confirm that I am happy with the release notes.

Comment 7

[Matthew Tuck [:CodeMachine]]

1b - Create new release tracking and release notes bugs for new milestone.

Comment 8

[Dave Miller [:justdave]]

Quick recap on the release procedure.  I'd *like* to make step 4 by noon EDT on
Wednesday the 29th, but it depends on getting the remaining docs bugs checked
in (I'm doubtful at this point).  All the code is frozen, it's all docs from here.

 1 - verify everything is final and close the tree.  No more last-minute
     fixemups after the tarball is posted! :-)  This means every 2.14
     targetted bug must be closed except this one.  That includes the release
     notes.
 2 - bump version number to 2.14 in globals.pl and check it in.
 3 - set cvs tags:
     a- cvs tag -FR BUGZILLA-2_14
     b- cvs tag -FR -rBUGZILLA-2_14 Bugzilla_Stable
 4 - make tarball:
     a- cvs checkout *** FROM [e-mail] ***
     b- cvs update -P to nuke the extra directories
 5 - repeat step 1 one more time just to be sure
 6 - upload tarball to ftp-staging
 7 - change version number to 2.15 in globals.pl and check it in.
 8 - upload release notes to www.moz.org/projects/bugzilla and make any fixups
     needed to the web page
 9 - sumbit news item to www.moz.org
10 - update http://freshmeat.net/projects/bugzilla/
11 - post announcement to netscape.public.mozilla.webtools
12 - post security advisory to netscape.public.mozilla.webtools and bugtraq.
     I think we can basically quote the "security bugs fixed" section of the
     release notes for this, and suggest they upgrade.
13 - file a Release Tracking bug for version 2.16
14 - file a Release Notes bug for version 2.16
15 - check in the patch tracker
16 - check in the query.cgi javascript changes
17 - update bugzilla.mozilla.org to the tip
18 - begin triage of contributed patches targetted at 2.16

Comment 9

[Jacob Steenhagen]

There are a couple links in faq.sgml (of the documentation) that also had to be
updated to query for 2.16 bugs instread of 2.14.  These are changed in the patch
on bug 97192 (that patch is currently not checked in).

Comment 10

[Jacob Steenhagen]

The three bugs that are slated to go in for mozilla.org's next update are:
Bug 84338 - The patch tracker
Bug 96534 - query.cgi speed improvements
Bug 28736 - Adding bug summary to dependency changed e-mails.

Comment 11

[Jacob Steenhagen]

Bug 75840 - Add the option to shutdown bugzilla durning syncshadowdb

(Yes, that makes 4, but not having this option was causing b.m.o's backups to fail)

Comment 12

[Matthew Tuck [:CodeMachine]]

Oh yeah, we released 2.14.

Comment 13

[Dave Miller [:justdave]]

all post-release activity in our list is completed.  Thanks for a great job on
the release guys!