From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xue Fuqiao Newsgroups: gmane.emacs.devel Subject: Re: Move to a cadence release model? Date: Wed, 11 Nov 2015 17:02:24 +0800 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1447232650 28461 80.91.229.3 (11 Nov 2015 09:04:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Nov 2015 09:04:10 +0000 (UTC) Cc: Richard Stallman , Emacs-devel To: John Yates Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 11 10:04:03 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZwRJy-0003KV-Gc for ged-emacs-devel@m.gmane.org; Wed, 11 Nov 2015 10:04:02 +0100 Original-Received: from localhost ([::1]:38748 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwRJx-0006bA-BR for ged-emacs-devel@m.gmane.org; Wed, 11 Nov 2015 04:04:01 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwRJI-0006Qj-Jw for emacs-devel@gnu.org; Wed, 11 Nov 2015 04:03:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwRJ0-0002Wq-3Y for emacs-devel@gnu.org; Wed, 11 Nov 2015 04:03:20 -0500 Original-Received: from mail-io0-x236.google.com ([2607:f8b0:4001:c06::236]:35747) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwRIP-0002P8-0l; Wed, 11 Nov 2015 04:02:25 -0500 Original-Received: by ioc74 with SMTP id 74so27958135ioc.2; Wed, 11 Nov 2015 01:02:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ioosSgSgVrLAYJGePc7AjC6PRpBPeMdbuD6cP90H0zs=; b=j7d1lead0rPxjL2towD39ctqvA5APJahyDqesx20ntpZMxMMaY2JjBcRznFpCL47+p fXw3Jghbd4MlgDpgx+RhUkjWFEucrCMWRZ1oleQTYZ/GundpeefHF5y1qXZoU7tQlSkK ifmEi6DL4zbSDeXwVLZjwcHidayPedTz7oz9jh5iY+/7BamDdOdt2bJYual7BKbtbfhC YfFbexy12MSGszp5u084YTofhjIG2ex2CmwkWJdyWYMHsOxFxpaTqpS2RMiL1jwRY7Iv KVwZsiEdab+orB+3ZPev/m6fD1iI32NERKLNrHOCZfSrx65o3ETn4BkyqPCA5uItfboS gPdw== X-Received: by 10.107.137.226 with SMTP id t95mr8054905ioi.188.1447232544473; Wed, 11 Nov 2015 01:02:24 -0800 (PST) Original-Received: by 10.79.94.2 with HTTP; Wed, 11 Nov 2015 01:02:24 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c06::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194038 Archived-At: On Wed, Nov 11, 2015 at 9:55 AM, John Yates wrote: Hi John, > I am unfamiliar with Firefox. I did read > https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ > but failed to get a good sense of how things work there. I've contributed to several Mozilla projects, and I know a bit about Firefox. I promise that I won't talk too much about this. If you're interested, we can discuss on the emacs-tangents list. Mozilla operates under a module ownership governance system[1]. The Firefox module owner and peers[2] review the code for Firefox. The "r+" flag on Bugzilla means that the code is accepted. Well, they do require that the patches should be small, functionally divided, including tests and with descriptive commit messages. Most Mozilla projects have two levels of review, known as "review" and "super-review". Reviewers look at the actual fix/feature/design and its maintainability/security/compatibility/localization/coding-style; super-reviewers look how a patch fits into the broader Mozilla codebase. Similiar to Chromium/LibreOffice/OpenStack, Mozilla also uses a code review platforms, such as MozReview[3]. For continuous integration testing, Mozilla uses/develops an extensive set of tools like Buildbot/TaskCluster and Treeherder. See https://developer.mozilla.org/en-US/docs/Continuous_Integration for details. [1] https://www.mozilla.org/en-US/about/governance/policies/module-ownership/ [2] https://wiki.mozilla.org/Modules/Firefox [3] https://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview.html