Re: RE: New SQL*Developer version numbers

Somebody please explain to me how the previous release numbering convention made more sense?  Was it that you liked to stump guests at parties with your ability to recall what release number came out in what year?  This isn't about copying Microsoft, this is about using logic.  Release year=release number, followed by release version.

Kellyn

Sent from myMail for iOS

Friday, July 14, 2017, 6:19 AM -0600 from rajendra.pande_at_ubs.com <rajendra.pande_at_ubs.com>:
>Gives the whole idea of release management a new meaning
>Now you will have to come up with a process to ensure that you don't release windows 2016 in 2017 :)
>Or have a process where the internal version numbers only get assigned after the last beta :)
>So anyone doing a beta doesn't know what version they are testing.. just in case the release bleeds into next year
>
>
>-----Original Message-----
>From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mladen Gogala
>Sent: Thursday, July 13, 2017 9:38 PM
>To: Tim Gorman
>Cc: oracle-l
>Subject: Re: New SQL*Developer version numbers
>
>Hi Tim!
>Year based releases? What a marvelously elegant idea! Release "Oracle SQL Server 2018" would avoid all the problems of the unlucky number 13. Hopefully, another vendor who also has year based release names, will not release SQL Server 2018. Maybe they should have an even-odd release system, just like parking in NYC?
>Regards
>
>
>On Thu, 13 Jul 2017 16:31:19 -0600
>Tim Gorman < tim.evdbt_at_gmail.com > wrote:
>
>> Perhaps Oracle is going to year-based releases?
>>
>> Neatly sidesteps all the "what comes after Oracle12" nonsense.
>>
>>
>>
>>
>> On 7/13/17 16:20, Mladen Gogala wrote:
>> > On July the 11th, there was an update to SQL*Developer and SQLcl. The previous version was 4.2. Now, I see this:
>> >
>> > SQLcl: Release 17.2.0 Production on Thu Jul 13 18:16:30 2017
>> >
>> > Copyright (c) 1982, 2017, Oracle. All rights reserved.
>> >
>> >
>> > SQL>
>> >
>> > Version "17.2"? Really? How did that happen? The same applies to SQL*Developer. Functionality is still pretty much the same, I haven't encountered any problems yet.
>> > Regards
>> >
>>
>
>
>
>--
>Mladen Gogala
>Oracle DBA
>Tel: (347) 321-1217
>--
>http://www.freelists.org/webpage/oracle-l
>
>
>
>Please visit our website at
>http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html
>for important disclosures and information about our e-mail
>policies. For your protection, please do not transmit orders
>or instructions by e-mail or include account numbers, Social
>Security numbers, credit card numbers, passwords, or other
>personal information.
>--
>http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l