contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: conan list "pkg/*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a