Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion What's next after Firefox 3 and Gecko 1.9?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Robert Accettura  
View profile  
 More options May 20 2008, 5:38 pm
Newsgroups: mozilla.dev.planning
From: "Robert Accettura" <rob...@accettura.com>
Date: Tue, 20 May 2008 17:38:12 -0400
Local: Tues, May 20 2008 5:38 pm
Subject: Re: What's next after Firefox 3 and Gecko 1.9?

On Tue, May 20, 2008 at 12:40 PM, Mike Shaver <mike.sha...@gmail.com> wrote:

> We should _break_ as few APIs as possible, but no fewer.  Additive
> changes to unfrozen APIs should be looked at with a kind eye, and more
> disruptive changes should come alongside a case for why the API break
> is significantly better than an additional new API or such clumsier
> alternative.

Is there any way to perhaps analyze source code of open source products out
there for what API's they are currently using?  So decisions could be made
with some data at hand?  Either spidering open sour svn/cvs/hg repo's or
perhaps even a script that could be run by the api user when they build, and
a report could be sent to some webtool that kept track of api's and number
of instances.

Then when deciding if it's worth breaking API _____, there's solid data on
who that effects outside of the mozilla tree.

--
Robert Accettura
rob...@accettura.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.