P: Lens metadata field missing on import

In other words, the official Adobe response is "we don't plan on fixing this issue until the next major dot release." If someone from Adobe had posted this in response to my original post a month ago, this would have been a disappointing, but at least honest and understandable statement given the underlying business and software development factors. It also would have allowed customers to decide for themselves whether this was an acceptable delay given their current needs, and whether rolling back was an acceptable workaround for them. But that didn't happen. Instead, we got the full story only after one month and a few vague "we're working on it, stay tuned" promises in the interim. I'm not at all surprised that this is how it unfolded, but I don't appreciate the lack of transparency.

At the moment, I'm willing to put up with the workaround and (begrudgingly) continue to pay for CC, because the older DNG converter still works with my existing gear. But I have a hard stop: I doubt the workaround will work for the D500 that I plan on upgrading to. I hope the fix is out by the time I get one, otherwise that could be enough to make me migrate off of Adobe software.

Apparently that's what they should have done with the .5 release so we wouldn't be in the predicament in the first place.

When one pays for a service, one expects reliability and promptness in fixing issues if
changes break something.  That is what a subscription is, a service!  As I said, Adobe was VERY PROMPT in charging me for this service!!!

As a manager of software development, I can tell you that putting out a release is a big deal, involving an insane amount of testing and verification. Each release carries a risk. If you can put out one release instead of two by delaying the release a few weeks, that is generally a better option. That said, some releases have to be rushed out because they contain critical fixes. This is not such a release, because there is a workaround to the lens exif problem. What I would have liked to have seen more of during this episode is more comments from people like Chen giving the community updates on the progress and schedule.

I am pleased to hear that fix is coming. I am, however, taken aback by the tone of your post and the suggestion that the timing of this release is in the hands of camera vendors. I bought a program that worked; Adobe, not the camera manufacturers, then broke it. Adobe is responsible for this, Adobe made it difficult for customers who continue to have to pay for the product because it's on a subscription model, and Adobe should have fixed this much more quickly.
This may not be the biggest issue in the world, and I do not want to make mountains out of lens data molehills - but  I -- like many other people who use the program and rely on lens information in our workflows -- had to scramble to find a workaround, which cost me a few hours of time. So -- please. When you acknowledge a problem, issue a mea culpa. Then fix the problem. And avoid, please, the (perhaps unintentional) dumping of responsibility for your issue onto third parties. Thank you.

It turns out that there are a coupe of newly announced cameras that the coming dot release would need to support. It took a little bit longer than the usual dot releases that had just the bug fixes. We're at the final stage to certify the build for release. Thank you for being patient. It is just unfortunate in terms of timing. We have zero influence over when the camera vendors will release their cameras.

Like that is going to happen!!  This has definitely made me consider dropping the subscription and looking for alternatives when I can do it without penalties.  Then again, by that time Adobe already has my money and doesn't care!  As I said, I am a very unhappy customer!!!!!!!!

Thesis getting ridiculous.  Has anyone gotten a refund from Adobe or their credit card?  

Almost a month now and still no fix for a broken update!!!!!!  But, Adobe has not delayed charging me right on time, without any hesitation for my subscription!!!!!!!

I am a very unhappy camper Adobe!!!!!!!!!!!!!!

Adobe has lost the ability to read/import/display the lens information in the NEF file in the Library module.
In Lr 5.7.1 I can see the lens model in the Library - Metadata view. In Lr CC 2015.5 I cannot (unless imported before 2015.5) when using the same NEF file.
Interestingly, in the Develop module, when applying Lens Correction it picks up the lens model automatically.