Re: New SQL*Developer version numbers

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Thu, 13 Jul 2017 21:37:38 -0400
Message-ID: <20170713213738.1b9efb06_at_umajor.home.com>


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
Received on Fri Jul 14 2017 - 03:37:38 CEST

Original text of this message