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
 |
Newsgroups: mozilla.dev.planning
From: John Vivirito <mozilla.extensions....@gmail.com>
Date: Sat, 07 Mar 2009 09:20:43 -0500
Local: Sat, Mar 7 2009 9:20 am
Subject: Re: Firefox 3.1 becoming Firefox 3.5
On 03/07/2009 04:25 AM, Dave Townsend wrote: >> I think extension developers would find this numbering scheme more For 3.5 or 3.2 they wouldnt be able to use 3.0*. As i recall that will >> beneficial. Then they wouldn't have to worry as much about their >> extensions breaking just because of maxVersion, since API breaks would >> typically occur at the first number. That way, maxVersion 3.* would >> cover until the next milestone. And it would be easier on the user >> base as well, because there are a lot of current extensions with >> maxVersion as their only issues. > Extension authors shouldn't have to worry about their maxVersion on only cover 3.0 security releases so in install.rdf it would be closer to 3.5* or 3.2*. As for the changes in versions, does this affect release times or is 3.5 still set to be released before 3.2? If not maybe bumping 3.2 to 3.6 or something like that this way it all stays inline. releasing 3.5 than releasing 3.2 might (most likely will) confuse end users. That would also caaause an issue with extensions devs i think. if they bump max version to 3.5 but the code changes in 3.2 might conflict with code in extensions. By no means am i against the version changes i just wanted to point out -- https://launchpad.net/~gnomefreak "How can i get lost, if i have no where to go"
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.
| ||||||||||||||||
