299318 - Document the Entire Release Process

Status: RESOLVED FIXED

(Bugzilla :: bugzilla.org, enhancement)

Description

[Max Kanat-Alexander]

The process of releasing Bugzilla involves a lot of stuff.

I wrote up some very long notes on exactly how to do it.

I'm going to translate them into HTML and put them on bugzilla.org.

Comment 1

[Max Kanat-Alexander]

Attachment: Text Notes

Here's my text notes on how to release Bugzilla. I'm pretty sure I already took
any important passwords out of it.

Comment 2

[Max Kanat-Alexander]

The URL field shows an actual version of what the page will look like.

Comment 3

[Max Kanat-Alexander]

Attachment: How To Release Bugzilla

OK! Here's the Release Process in all its glory, in HTML. It's quite long.

As far as I'm aware, justdave is the only person other than me who's ever done
a release, so he's the only person able to really make sure that I got
everything in there. :-)

Comment 4

[GavinS]

Minor typo in the 'Making the Diff Files' section:

> "You have to edit it an make a new "

_and_ make a new?

Comment 5

[Max Kanat-Alexander]

(In reply to comment #4)
> > "You have to edit it an make a new "
> 
> _and_ make a new?

  Oh, thanks! Fixed in the landfill version. :-)

Comment 6

[Dave Miller [:justdave]]

Comment on attachment 188011 [details]
How To Release Bugzilla

> Motivate People

>    2. Put a link at the very end of the topic line, with that tinyurl.

Topic line of what?  Mention IRC or something :) (which channel might be nice,
too :)

>    1. Check-out a copy of bugzilla.org from CVS, to apply your patches to. The best place to do this is on landfill, because it already has the environment set up to do it. Make sure you have checkin access on cvs-www.mozilla.org.
> 
>       The CVS info is:
> 
>       CVSROOT=:pserver:[e-mail]:/cvsroot

Not sure how wide the intended audience is, but for purposes of people helping
out, might not hurt to mention this is available anonymously from
CVSROOT=:pserver:[e-mail]:/www

> Tag the Releases in CVS
> 
> You need to create CVS tags for each new release, and move the -BRANCH and _Stable tags. Because of the way CVS works, it's easiest to delete the old tags and then tag the new releases. For example, here's the series of commands I used to tag the 2.18.1, 2.19.3, and 2.16.9 releases:

OK, this is all screwball...  I'm just going to give you a new list instead of
pointing out corrections to yours because it'll be easier that way :)

cd /var/www/html/mkanat218/
cvs update -dP -rBUGZILLA-2_18-BRANCH -C
cvs tag -FR BUGZILLA-2_18_1

cvs update -dP -rBUGZILLA-2_18-STABLE
cvs tag -R -d BUGZILLA-2_18-STABLE
cvs update -dP -rBUGZILLA-2_18_1
cvs tag -FR BUGZILLA-2_18-STABLE

cvs update -dP -rBugzilla_Stable
cvs tag -R -d Bugzilla_Stable
cvs update -dP -rBUGZILLA-2_18_1
cvs tag -FR Bugzilla_Stable

cd /var/www/html/mkanat216/
cvs update -dP -rBUGZILLA-2_16-BRANCH -C
cvs tag -FR BUGZILLA-2_16_9

cvs update -dP -rBUGZILLA-2_16-STABLE
cvs tag -R -d BUGZILLA-2_16-STABLE
cvs update -dP -rBUGZILLA-2_16_9
cvs tag -FR BUGZILLA-2_16-STABLE

cd /var/www/html/checkinmkanat/
cvs update -dP -CA
cvs tag -FR BUGZILLA-2_19_3

> Send Security Advisory

The security advisory should be GPG signed with a key that has its public half
either available on the public keyservers or from the bugzilla.org website.

Comment 7

[Max Kanat-Alexander]

Attachment: v2

OK, I addressed your comments.

Comment 8

[Max Kanat-Alexander]

RCS file: /cvsroot/mozilla-org/html/projects/bugzilla/docs/release.html.tmpl,v
done
Checking in docs/release.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/docs/release.html.tmpl,v  <-- 
release.html.tmpl
initial revision: 1.1
done