Yeah, thanks Juniper for taking a year to fix a critical tool for network engineers.
I'll be right back, I just upgraded one of my Juniper devices and now my network is on fire. On 05.08.19 09:12, Chris Lee wrote: > And it's 5th August and as promised in the last KB update PR Search > functionality is now back online! Thank you all at Juniper who worked on > restoring this to service! > > On Fri, Aug 2, 2019 at 11:58 PM Richard McGovern <rmcgov...@juniper.net> > wrote: > >> I am doing some new checking. I am like 99.9% sure the floppy disk idea >> will not fly -__ >> >> Hopefully I will have an update sometime next week. Enjoy your visit to >> San Jose. >> >> Regards, Rich >> >> Richard McGovern >> Sr Sales Engineer, Juniper Networks >> 978-618-3342 >> >> I’d rather be lucky than good, as I know I am not good >> I don’t make the news, I just report it >> >> >> On 8/1/19, 9:26 PM, "Nathan Ward" <juniper-...@daork.net> wrote: >> >> Hi, >> >> Was reminded of this today. I see that basic search will be fixed by >> 2019-08-05 - but still no comparison between releases which really is the >> key thing that people want. >> >> I’d like a dump of all the PRs and “fixed in release x” details, so I >> can build my own PR search tool and make it available to the community. >> >> I believe I can extract new PR details from the email subscription - >> but I won’t have history. >> >> I can just query it in a loop starting at PR1, but, perhaps it would >> be easier to get a dump of them? >> >> >> I’m in San Jose next week - can pop up the road with a floppy disk or >> two if it’s hard for Juniper IT to send me a big file? >> >> > On 14/05/2019, at 11:49 AM, Richard McGovern <rmcgov...@juniper.net> >> wrote: >> > >> > Nathan, not sure what history you are seeking, but if tell me what >> PR listing you seek, I'll see what I can gather. >> > >> > Richard McGovern >> > Sr Sales Engineer, Juniper Networks >> > 978-618-3342 >> > >> > >> > On 5/13/19, 9:25 AM, "Nathan Ward" <juniper-...@daork.net> wrote: >> > >> > >> >> On 14/05/2019, at 1:17 AM, Nathan Ward <juniper-...@daork.net> >> wrote: >> >> >> >> >> >>> On 9/05/2019, at 11:52 PM, Richard McGovern <rmcgov...@juniper.net >> <mailto:rmcgov...@juniper.net>> wrote: >> >>> >> >>> Nathan, I am not sure what you want to hear, or what would make >> you satisfied, but YES Juniper [IT?] did screw-up, and a restore from >> back-up was/is not possible. So this situation is now being worked on, >> unfortunately at a not so fast pace. I hope you decide to stay with >> Juniper, as I feel there are far worse things one could be concerned about >> than this. >> >> >> >> Well, I was hoping that someone had an archive of it all somewhere. >> > >> > Actually. >> > >> > There’s a PR subscription service mentioned in that KB. >> > >> > If I sub, I only get future. Can you or someone else provide me >> with a history of that? >> > >> > -- >> > Nathan Ward >> > >> > >> > >> > >> >> >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp