[c-nsp] 12.2SXF?

[Rodney Dunn]

Just because you see it as a new feature doesn't always mean
that. A lot of times the code is in SXF when the throttle is
first pulled but we just can't get it all tested. When we do
it comes up as "activated" ie: supported on a later release
in the throttle.

If the business demands it features will go in but we try very
hard to make that a very rare exception. The possibility will always
exist.

Rodney

On Fri, Oct 13, 2006 at 11:21:44PM +0200, lists at Hojmark.ORG wrote:
> Tim,
> 
> Your explanation below (and the system itself) made a lot of
> sense to me. Do you know why the 'occasional exceptions' became
> the norm in SXF, especially SXF2 and SXF5, which has a *lot* of
> new features?
> 
> TIA,
> -A
> 
> > -----Original Message-----
> > From: Tim Stevenson [mailto:tstevens at cisco.com] 
> > Sent: Wednesday, August 17, 2005 12:57 AM
> > To: lists at hojmark.org; 'Rodney Dunn'
> > Cc: 'cisco-nsp'
> > Subject: RE: [c-nsp] 12.2SXF?
> > 
> > No, not really.
> > 
> > SX[A,B,D-F] are new feature releases. A rebuild w/only bug 
> > fixes on one of these is followed by another numeral, ie, SXD4
> > is the 4th rebuild of SXD. 
> > It has no new features, just bug fixes over SXD3, which has 
> > only bug fixes over SXD2, etc.
> > 
> > There are (of course) occasionally exceptions to this (a 
> > minor new feature slips into a rebuild). These are generally
> > rare.
> > 
> > Tim
> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/