MSVC 14.38

[h-vetinari]

Microsoft recently released VS 17.8, which will presumably make it into the default images soon (and would break the vs2022 compilers then, see #67).

I tried to update a while ago, but had to chase down a conda-smithy bug (could not rerender recipe anymore for some reason...).

Closes #69

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

• It looks like the 'vs2015_runtime' output doesn't have any tests.
• It looks like the 'vc' output doesn't have any tests.

[h-vetinari]

@conda-forge/vc, this is ready, PTAL :)

[h-vetinari]

Gentle ping @conda-forge/vc

[isuruf]

I was going to ask you to check that the azure and gha images have been updated. Otherwise this would break builds. Please stop merging in feed stocks that you are not a maintainer of without asking for a review from core. This is an abuse of power. This has happened multiple times. I will bring it up next meeting.

[isuruf]

Cc @conda-forge/core

[h-vetinari]

Please stop merging in feed stocks that you are not a maintainer of without asking for a review from core. This is an abuse of power.

You know that I've been involved on this feedstock for quite a while and I consider myself a maintainer here, whether I'm in meta.yaml or not. I'd appreciate if you could avoid throwing around words like "abuse", because if this is abuse, I'm handing in my keys voluntarily.

[isuruf]

Yes, I do consider it abuse. I really really appreciate your work in conda-forge, but the way you go about it by pushing everyone's buttons is wrong. Please follow the processes in place. If you can't, please do.

[h-vetinari]

So if I add myself to the meta.yaml here (which would be justified based on previous involvement here and in our compiler stack generally), it magically would stop being abuse?

Please follow the processes in place

The guideline was "wait for a response for two weeks", which I did.

[isuruf]

So if I add myself to the meta.yaml here (which would be justified based on previous involvement here and in our compiler stack generally), it magically would stop being abuse?

After the interaction here I wouldn't accept such a PR anyway.

The guideline was "wait for a response for two weeks", which I did.

No, the guideline is to wait for a week or two and ask someone else from core to merge.