Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Process: Difference between revisions
Jump to navigation
Jump to search
fill in the "creating builds" section
m (we need CLIENTTAG now) |
(fill in the "creating builds" section) |
||
| Line 67: | Line 67: | ||
== Creating Builds == | == Creating Builds == | ||
'' | Once the cvs-mirror has updated the tagging changes, it's time to log into our release machines. Those machines on all the primary platforms have the latest {bug | ||
343891} patch applied so that we can create (stub) installers with the correct URLs in them right out of tinderbox. | |||
So, I'm logging into those boxes, cd to the release-seamonkey-1.1 directory and execute "./tinderbox clobber restart" there, which does a BuildOnce clobber run producing the builds. Note that only Linux can do this from the remote ssh shell, Mac is done via VNC from a terminal window and Windows via RDP from a cmd window, so all of them can perform basic tinderbox tests on the builds. | |||
The Linux machine has additional stuff added to produce source tarballs. I have a script there that does | |||
export MOZ_POSTFLIGHT_ALL="~/tinderbox/Makefile.tarball" | |||
before starting the tinderbox run, and here's the Makefile.tarball file: | |||
DEPTH = $(MOZ_OBJDIR) | |||
topsrcdir = $(TOPSRCDIR) | |||
srcdir = $(TOPSRCDIR) | |||
VPATH = $(TOPSRCDIR)<br> | |||
include $(MOZ_OBJDIR)/config/autoconf.mk<br> | |||
include $(TOPSRCDIR)/config/rules.mk<br> | |||
include $(TOPSRCDIR)/toolkit/mozapps/installer/package-name.mk<br> | |||
SRC_TAR_BASE = $(MOZ_PKG_APPNAME)-$(MOZ_PKG_VERSION).source<br> | |||
postflight_all: | |||
tar --directory=$(TOPSRCDIR)/.. -cjf $(TOPSRCDIR)/$(MOZ_OBJDIR)/dist/$(SRC_TAR_BASE).tar.bz2 mozilla | |||
tar --directory=$(TOPSRCDIR)/.. -czf $(TOPSRCDIR)/$(MOZ_OBJDIR)/dist/$(SRC_TAR_BASE).tar.gz mozilla | |||
This enables us to conveniently provide a source tarball from exactly the same state and upload it to stage together with the release builds. | |||
All the boxes are configured to upload into a candidates-seamonkey1.1.5/ directory in my personal home dir on stage, while the ftp_url points to the final location on releases.mozilla.org. This enables me to both move that candidates dir to the SeaMonkey nightly dir on public FTP for testing as well as to later copy those builds directly to the release location without any further change, given this candidate is made final after QA. | |||
== Doing The Actual Release == | == Doing The Actual Release == | ||
''TODO'' | ''TODO'' | ||