12.0 was feature frozen back in the dark ages, which is why
the support you're looking for is only in 12.0T, since 12.0
gets only bugfixes tell EOS.
If 12.0(7)T does all you need and evokes no catastrophic bugs,
use it and be happy, otherwise you have to go to 12.1 to pick
up active maintenance again.
It's vaguely possible that support might also pop up in 12.0S.
only Cisco would know what's in the pipeline there.
George
> From goemon@anime.net Sun Feb 11 22:14:09 2001
> Date: Sun, 11 Feb 2001 19:03:56 -0800 (PST)
> From: Dan Hollis <goemon@anime.net>
> To: Frank Bruce <fbruce@cisco.com>
> cc: George Robbins <grr@netaxs.com>, <cisco-nsp@puck.nether.net>,
> <nathan@arteck.com>, <vac@dsqworld.com>
> Subject: RE: [nsp] REG: Cisco IOS Software
> In-Reply-To: <NCBBKHJALJOEFINPNFJGIEHOICAA.fbruce@cisco.com>
>
> On Mon, 12 Feb 2001, Frank Bruce wrote:
> > You'll see from the map that in the future many of the release trains with
> > new features converge on the 12.1 major release, you'll note there are no
> > letters involved, and it's not deferred.
>
> Thats nice, what about a 12.0 major release then. (Which was my original
> question). If IMA it made it into 12.1(1) you would think 12.0(16) or
> something would be next.
>
> -Dan
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:28 EDT