Path: g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 02 Jun 2006 00:17:47 -0500
Return-Path: <mbeltz...@gmail.com>
X-Original-To: dev-plann...@lists.mozilla.org
Delivered-To: dev-plann...@lists.mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=E+KDuhHkuHCzern0R1884lfwdp7WrtKZubUp0HbTQEDfVlk+4ihvEKG1bxp++N29RZ7j+orcdndi6Oc/Wx3JJlaEnyx/b4qErALhtSVVYu5lxZG6O5exnrGzW3EAykGtW480T/xCLt4lcFhmrLf3ceDmloYI7T6qb2NnoM67ht8=
Date: Fri, 2 Jun 2006 01:17:44 -0400
From: beltzner <mbeltz...@gmail.com>
To: dev-plann...@lists.mozilla.org
In-Reply-To: <20060602051016.GA17135@ridley.dbaron.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060602051016.GA17135@ridley.dbaron.org>
Subject: Re: interface stability policy on 1.8 branch
X-BeenThere: dev-plann...@lists.mozilla.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dev-planning.lists.mozilla.org
List-Unsubscribe: <https://lists.mozilla.org/listinfo/dev-planning>,
	<mailto:dev-planning-requ...@lists.mozilla.org?subject=unsubscribe>
List-Post: <mailto:dev-plann...@lists.mozilla.org>
List-Help: <mailto:dev-planning-requ...@lists.mozilla.org?subject=help>
List-Subscribe: <https://lists.mozilla.org/listinfo/dev-planning>,
	<mailto:dev-planning-requ...@lists.mozilla.org?subject=subscribe>
Newsgroups: mozilla.dev.planning
Message-ID: <mailman.2679.1149225467.30817.dev-planning@lists.mozilla.org>
Lines: 25
NNTP-Posting-Host: 207.126.111.250
X-Trace: sv3-koaCscGWuxvxr3QhstwPD1fJJlHLmvtox4yKgbaMire+DIRCZMIjUuEH66J5RJu5cQO6U9rJL5aDvis!FsL7yweN7FwR7+kydNnUF4BBB2/Nq/Uaj/q3luVsljxdS4hzHuVAkzQ3gcd9RJDL6FePi1yqbD/k!2VDiliTyUJOq0+hGKOij2bwkJ9tP2dxX1m/C
X-Complaints-To: ab...@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.32

On 6/2/06, L. David Baron <dba...@dbaron.org> wrote:
>  1. Who decided on this policy?

As I recall, this policy came out of the December Firefox Developer's
Summit in a session organized by Brendan on branch management.

>  2. What is the goal of this policy?  (i.e., why do we have it?)

The goal was to minimize the impact of Firefox 2 (a primarily
front-end update to Firefox 1.5) on our extension development
community by not revving the APIs unless absolutely necessary, thus
enabling most existing extensions to "just work" with Firefox 2 (once
they'd been smoketested and had their maxVers bumped, natch).

>  3. What exactly does it mean?  (i.e., what counts as an interface)

Here I can't help you. Connor? Brendan? FWIW, though, I've heard
rumours that SafeBrowsing ended up chaging some existing APIs in
addition to adding some. Not sure if or how that decision was made
properly.

cheers,
mike
-- 
/ mike beltzner / user experience lead / mozilla corporation /