[j-nsp] Junos 21+ Killing Finger Muscle Memory...

[C K]

Indeed. And as you’re alluding to and most probably already know this — yeah most of us end up settling on “some release train” for a while, after we spend 3-4 months testing it thoroughly in the Lab... then spend 18 months getting everything in the network “up to that release”. With hundreds of beefy devices spread across the globe, and having to do customer notifications to each and every service, (and get them to also agree on the time that we’re doing it.. some of my customers have a LOT of weight, and can say ’no’), it does take quite a while to get through it all.

And yup - by that time, 2+ years has gone past, and it’s time to do it all over again. Lather, rinse, repeat. ;)

FWIW — The last one I personally did testing on for our LAB and production network was 20.4Rx-Sxx (EEOL version)….. so yeah, we started running into this new “sh[tab] rou[tab]” command in the Lab in the last few months as we started our tests on 21.4 and 22.4 (the next EEOL candidates for a global rollout)

It is what it is. ;)

My hope is that it’s ‘not too late’ to fix this slightly-annoying UI/UX experience and this can be pulled back from the jaws of defeat before it gets entrenched too far. as Mark said, If it gets looked at, great. If it doesn't, it's not the end of the world; but if we, as customers, don’t provide useful and constructive feedback to Juniper (something they’re asking fro with their outreach programmes, the Elevate community, the Juniper circle, etc..) then it has a 100% chance of never getting looked at. 

- CK.


FWIW — The contrarian position would be if I were to simply just blindly install “oh hey, theres a new JunOS” every 3-4 months, and we get a nasty VPLS bug, or an eVPN bug, or an HQoS Bug, or an ISIS/SR bug which causes an outage/customer issue, I’d quickly find myself with a pink slip. ;)



> On 16 Jul 2023, at 4:54 am, Crist Clark via juniper-nsp <juniper-nsp at puck.nether.net> wrote:
> 
> I find it kind of telling that customers are just getting around to
> complaining about it two years after it was released. Not at all
> surprising, but illustrates how slow network operators update cycles can be
> compared to the pace of development.
> 
> To the Junos developers, this is ancient news, long forgotten in the dozens
> of sprints and multiple releases since.