I know I'm just some bro on the list here but I'd agree. I don't think you want to turn the SDK into firefox/chrome, where every time they push the build button it goes up a full revision. In a month we'll all be browsing with firefox/chrome 135.
On Mon, Dec 8, 2014 at 4:04 PM, Subscriptions <subscripti...@leeburrows.com> wrote: > Hi > > IMO, updating version number from 4 to 5 (or 14 to 15) should be saved for > major changes (think halo to spark). New releases that only contain a few > new features and bug fixes should be relegated to 0.1 numbers. > > As for changing the system, my feeling is if it isnt broken dont fix it... > we risk confusion for new users with similarly numbered but unconnected > AIR/Flash player versions and 'copying' Adobe could hurt perceptions of our > independence. > > Lee Burrows > ActionScripter > > > On 08/12/2014 20:22, OmPrakash Muppirala wrote: > >> We have a pretty big release coming up [1]. I am wondering if it is time >> to bump up the version number to 5? >> >> As an alternative, we could simply drop the '4' from 4.14.0 and simple >> start versioning our releases as 14, 15, etc. >> >> Technically, we need to make sure that either option would work with IDEs >> (especially Flash Builder) and our own version checking logic in the SDK. >> >> Any thoughts on either of these suggestions? >> >> Thanks, >> Om >> >> [1] https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES >> >> > -- Jesse Nicholson
