Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
Recently, the Mozilla Release Engineering team has made numerous advances in release automation for our browser, Firefox. We have reduced the requirements for human involvement during signing and sending notices to stakeholders, and have automated many other small manual steps, because each manual step in the process is an opportunity for human error. While what we have now isn't perfect, we're always striving to streamline and automate our release process. Our final goal is to be able to push a button and walk away; minimal human intervention will eliminate many of the headaches and do-overs we experienced with our older part-manual, part-automated release processes. In this article, we will explore and explain the scripts and infrastructure decisions that make up the complete Firefox rapid release system, as of Firefox 10.
is this a reprint of an old article? (still interesting, but just wondering)
update: oh, it's an extract from a book. that explains the age...
greetings, eMBee.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
update: oh, it's an extract from a book. that explains the age...
greetings, eMBee.