SSE4

> We don't write side by side in the documentation: _"A will have breaking changes. We recommend you to use A. Any alternative to A is deprecated"_. IMHO it is...

the first time I have seen SCM feature I was thinking it's just a syntax sugar for: ``` def source(self): self.run("git clone https://github.com/myorg/myrepo.git") ``` with the SCM equavalent: ``` scm...

it's not obvious where file should be created. is it conan cache, or current directory? yes, some examples would be nice to illustate how should I configure that file.

adding @uilianries. we recently archived conan-community. btw, I am not sure if we still need these go instructions at all.

yes, I think we need a better reference for reference (sic!) probably extracted from https://docs.conan.io/en/latest/versioning/revisions.html with some additions. I would make some clear distinctions between RREF and PREF formats (recipe...

if we talk not only about CCI, but about general usage, the API seems to be an easy to misuse in general, and warnings in docs isn't going to address...

> I'm not opposed to changing the tool implementation and change the docs accordingly. But, if that is the case, the proposal should start in `conan-io/conan` repository defining new behavior,...

lemme explain my vision a bit :) the tool was designed, and does what is documented, it's fine. however, we already have a proof the tool itself is not sufficient...

the possible explanation for the current situation might follow the structure: - if you're supplying `compiler.cppstd` setting, then do X - if you're not supplying `compiler.cppstd` setting, then do Y...

yes, totally agree, in my opinion, we have to use the following algorithm: 1. scan project items for `conanfile.[txt|py]` 2. scan solution items for `conanfile.[txt|py]` 3. scan directories, like it's...