[c-nsp] T releases and bugs...??

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Foster wrote:
> Wonder if anyone can shed some light on the .T release trains.  Do they contain bug fixes for features released in the previous .T release ie:
>  
> Mainline release = 12.4.(4)
> Technology release = 12.4(4).T
>  
> Bugs for feature x and y found in .T release....
>  
> Fixed in release 12.4(5).T...
>  
> If this is not the case how are bugs handled in the .T release trains...
>  

See
http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml#t4


In general, bugs found and fixed in 12.4 mainline will appear in a
subsequent release of 12.4T.  Remember that mainline and 12.4T are not in
maintenance numbering sync (they actually share the 12.4(x) numbering
space) so there would not be a 12.4(4) and 12.4(4)T.  Instead you will see
that there has been a 12.4(3), 12.4(4)T, 12.4(5), and then 12.4(6)T.  So
bug fixes post 12.4(3) should appear in 12.4(4)T and 12.4(5) and so on.

When critical bug fixes are applied to an open 12.4T release, you get a
renumber build like 12.4(4)T1.  The last number will increment with each
subsequent rebuild.  There may also be occasion where there are multiple
12.4T versions open and active at one time.   So, if 12.4(4)T is active,
12.4(5) has been released, and a bug is fixed that would appear in
12.4(6)T, the bug could not be sync'd between release trees and would be
manually applied to the 12.4(4)T release.

Naturally, bugs that affect only features that appear in the T release will
only be fixed in the T release.  However, they may have to be applied to
multiple open releases of the T train as above.


- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFWQITE1XcgMgrtyYRAvszAJwMsHnlk9sLookIFEtIAl2jVUi12gCgmOeX
iiZ/WhMR6l6FLX+LDi/5YU0=
=cEts
-----END PGP SIGNATURE-----