Path: g2news2.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 16 Mar 2011 15:18:17 -0500
Return-Path: <benja...@smedbergs.us>
X-Original-To: dev-plann...@lists.mozilla.org
Delivered-To: dev-plann...@lists.mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Received-SPF: neutral (smedbergs.us: Domain does not state whether sender is
	authorized to use 'benja...@smedbergs.us' in 'mfrom' identity
	(mechanism '?all' matched)) receiver=notorious.mozilla.org;
	identity=mailfrom; envelope-from="benja...@smedbergs.us";
	helo=dm-mail03.mozilla.org; client-ip=10.2.74.48
Date: Wed, 16 Mar 2011 16:18:01 -0400
From: Benjamin Smedberg <benja...@smedbergs.us>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Chris Jones <cjo...@mozilla.com>
Subject: Re: Proposed post-Fx4 rapid release process
References: <SvudndfOP7vZlxzQnZ2dnUVZ_vKdnZ2d@mozilla.org>
	<4D8118BD.9000500@mozilla.com>
In-Reply-To: <4D8118BD.9000500@mozilla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dev-plann...@lists.mozilla.org
X-BeenThere: dev-plann...@lists.mozilla.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Planning for future releases <dev-planning.lists.mozilla.org>
List-Unsubscribe: <https://lists.mozilla.org/options/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.1867.1300306697.4383.dev-planning@lists.mozilla.org>
Lines: 14
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 63.245.208.166
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-coVOQMRNmjlYFeUPwWrjkGOIFJmsqg+spfmmu2kPRydiZykKeo6PUfY90aumQOkPLPhtU9rAmn3Fl/F!oPB1iK7c95EeXy1YRsbEEkyFWqZsPAEAAGYfHuI1RtfuOjEYslUGG+OVStAt/0GjZSeJe10binNo!WK06Bua3OpTVn0IY4MevUfpbunDhqMOsag==
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.40
X-Original-Bytes: 3071

On 3/16/2011 4:08 PM, Chris Jones wrote:
> On 03/16/2011 02:06 PM, Robert Sayre wrote:
>> Let's work together to iron out any bugs in the document.
>
>  - Does "extension compatibility" (whatever that may end specifically 
> meaning) include binary extensions?  Would we disable a new feature if 
> some extension(s) weren't made compatible with it in time for 
> scheduled release?
We should expect that extensions may need to be updated for each 
release. In particular, I expect that we will revise the XPCOM binary 
component version number for pretty much every release.

--BDS