P: Most functions in Edit, Image, Layer, Select and Filter grayed out for image opened from LrC

I mean you seem like someone who just likes to hear themselves talk but you really have a vague understanding of U.S. law when it comes to software. Also, no I am a professional based on the salary paid to do the work I do. Also, just because you request something doesn't mean I have to give it to you. You really just seem like yet another internet troll. And if you don't mean to be, I suggest altering your language. 

Also, you speak upon Adobe's behalf out of faith? Because from what I see you have no affiliation with them. So you speak as if you know but have no real connection? Kind of confused on your angle of discussion here. 

And no, nothing is bug free, but at the same point, I don't have recurring issues that Adobe seems to be having with products like Word, Capture One, Davinci Resolve, Solid Works, Blender, Excel, Madcap Flare, et ceteral, all which I use on an almost daily basis. But please, continue to berate because you really don't know any better.
Enough said. 

I am a beta (and alpha) tester <g>
I've written Release Notes too. For an Adobe PS Automate plug-in. 

I make informed decisions by informing myself and that means research. Adobe in fact provides numerous methods of informing users; blogs (stay tuned.... can't say more but keep an eye on em), on their actual web site, in their UtoU forums and within their own software.

Which then forces Adobe's users to hunt down every bug and new "feature" as they encounter them.  Any wonder that many feel like they're your beta testers?

BTW, I know what RN's are.  I've helped write them.  They're a list of non-compliant functions you know of from testing (along with changed behaviors).  What I'm proposing is that rather than a static document, a live list of what has been found post release be published.  Surely that list is being kept internally (I would hope).  The volume of posts on this topic alone should be informing someone that a better way to communicate that information needs to be found.

Think of it this way; How would you make an informed decision to upgrade if the only way to know, is to scan multiple forum posts which may or may not be labeled with the release ID and which may or may not be user error?

The EULA which you still haven't read does protect Adobe from the so called and absolutely silly idea of a class action but by all means, waste your time venting and going down that rabbit hole, while the fix is already known and a software update will come soon. 

That you use LR to do a larger portion of photography doesn't answer the question, even if you are not a hobbyist, as I suspect you are, you don't have a leg to stand on with this bug legally and a quick but through read of the contract you agreed to, just to access the software, would show. I'm not saying it's not professional software whatsoever, it is, I'm saying you're probably not a professional user of that software but that's moot if and when you read the contract with Adobe you agreed upon to then launch the software. 
Have you not figured out how to bypass this bug? A bug that will, in time, be fixed?
Again, do tell us what software products you use, professionally or as a hobby that is 100% bug free. Of course, you cannot. 
Enough said. 

Actually, not really. EULAs do not protect a company from everything, much like how wavers don't really protect doctors. Such suits are currently open against both Symantec and Oracle. Additionally, there are bugs and continuous bugs, and just plain negligence. I do work in the development world, I work with testers on a daily basis, software architects, et cetera, and when this many bugs exist and continue to get past testing and dev, people are reprimanded or fired.

And yes, I use LR, as do a large portion of photographers, Are you saying its not professional software? Care to keep making brown nosing Adobe arguments?

Release notes are provided with an actual release. 
The temporary fix is found here and elsewhere on the web in various forums. That's one reason Adobe and other's host such forums. 

OK, then how about some release notes that document the problems found so far and workarounds if available?  I get that this isn't a showstopper, but proactively telling your install base what they can expect would go a long way.

I just opened an image in the newly update PSCC and there is NO OPTION to duplicate the layer?? It opned from LRCC as a locked background. I unlocked it and CTL-J does not work, Duplicate option is greyed out on both a right click and from the layer dropdown?? The layer says it is Layer 0 and there is NO OPTION to duplicate. WTF???

It's running thin because you have really no idea how software development function.
Bug has to be internally verified on different hardware and differing OS versions. Bug has to be fixed and testing the same way. Beta has to be released for the same testing. Installer has to be updated as do web sites. Documentation has to be updated. One bug alone is rarely updated too. As an actual Adobe software developer and alpha/beta for them, since 1992, I actually understand how this work takes place. And now you kind of do. Relax! When it's done, it's done.
Then there will be other bugs in every software program and the bitching and moaning can start all over again. ;-(

Three weeks without an update? My patience is running a bit thin