Message from discussion
Firefox 3.1 becoming Firefox 3.5
Path: g2news1.google.com!news1.google.com!Xl.tags.giganews.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, 06 Mar 2009 14:43:23 -0600
Return-Path: <sdwi...@mozilla.com>
X-Original-To: dev-plann...@lists.mozilla.org
Delivered-To: dev-plann...@lists.mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Date: Fri, 06 Mar 2009 12:40:55 -0800
From: Shawn Wilsher <sdwi...@mozilla.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US;
rv:1.9.1b3pre) Gecko/20090301 Lightning/1.0pre Shredder/3.0b3pre
MIME-Version: 1.0
CC: dev-plann...@lists.mozilla.org
Subject: Re: Firefox 3.1 becoming Firefox 3.5
References: <mailman.259.1236280716.4688.dev-planning@lists.mozilla.org> <4JWdnS3EgOe67SzUnZ2dnUVZ_tPinZ2d@mozilla.org> <zL2dndWeyIuo7yzUnZ2dnUVZ_j2WnZ2d@mozilla.org> <ZPmdnfiCXfUw5SzUnZ2dnUVZ_q3inZ2d@mozilla.org> <mailman.50.1236368209.4415.dev-planning@lists.mozilla.org>
<uKudnRnk2uN44izUnZ2dnUVZ_qLinZ2d@mozilla.org>
In-Reply-To: <uKudnRnk2uN44izUnZ2dnUVZ_qLinZ2d@mozilla.org>
Content-Type: multipart/mixed; boundary="------------050705020508030204040308"
X-Content-Filtered-By: Mailman/MimeDel 2.1.11
X-BeenThere: dev-plann...@lists.mozilla.org
X-Mailman-Version: 2.1.11
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.67.1236372202.4415.dev-planning@lists.mozilla.org>
Lines: 40
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 63.245.208.166
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-yY5QFy5K/AcDYsMzFWxArJdmLDPUXdmQGvAhyBQ3hRnrlAP6eTWyW+JR0Ce65+RHyikRIa/TAzYTsFh!rhHmv+AU3JJgfJS/PbsIpX8jzcm6lYijESzX14WJ6LkBkG6Cie538P3MATGCxYmL7R8FA/Ir+WnM!kMN7eO1/i+r6kQfnbQGNH4gNcp7Wt3U=
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.39
This is a multi-part message in MIME format.
--------------050705020508030204040308
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 3/6/09 11:59 AM, John J Barton wrote:
>> On 3/6/09 11:29 AM, John J Barton wrote:
>>> I suppose this all seems trivial from the inside. It's not the version
>>> checking that is any issue, it's the toll in human communications. Bug
>>> reports, email, news postings all refer to 3.1. These all refer to
>>> something that is now gone. Yes another version will come out called
>>> 3.5, but '3.1' does not go away.
>> Might I suggest that you use codenames (Shiretoko) in the future then?
>> Codenames are created for a reason.
>
> That won't work here:
> this.ff3p1 = versionChecker.compare(appInfo.version, "3.1*") >= 0;
I'm a bit confused here. You said it is not version checking that is a
problem, but that it is human communication that is the issue. I then
suggested code names, and then you argued that that doesn't work in
version checking code. It almost looks like you are arguing for the
sake of arguing here, which I don't think you actually mean to do. Can
you please clarify?
> Plus it's not practical because users don't say that, they say 3.1.
Perhaps that's because developers say 3.1, so that's what users
associate? This seems a lot like a chicken and egg problem, honestly.
> This part I don't get: why wouldn't users be delighted with a bulging
> new 3.1?
The same kind of reasons why some users don't like the new location bar
in Firefox 3.0. Big changes are scary to users. Small version bumps
imply that there aren't many changes, whereas bigger ones imply that
there will be more. It's psychological.
Cheers,
Shawn
--------------050705020508030204040308--