Skip to content

README: replace build badges column with MSRV#337

Merged
newpavlov merged 2 commits intomasterfrom
readme_msrv
Jul 13, 2021
Merged

README: replace build badges column with MSRV#337
newpavlov merged 2 commits intomasterfrom
readme_msrv

Conversation

@newpavlov
Copy link
Copy Markdown
Member

I think MSRV information is more valuable than the build badges, especially considering that in this repository we have crates with 3 different MSRVs.

Also I've removed the aes-ccm mention, since the ccm crate should be preferred for now. Later we probably should introduce a folder with crates containing common common composition of primitives (AES-GCM, ChaCha20Poly1305, etc.).

@newpavlov newpavlov requested a review from tarcieri July 11, 2021 02:50
@tarcieri
Copy link
Copy Markdown
Member

Alternatively we could get all of the MSRVs in sync, e.g. 1.51+.

That would make it possible to re-unify the heapless tests in the workflows, and set resolver = "2" for the whole repo.

@newpavlov
Copy link
Copy Markdown
Member Author

I don't think we should bump MSRV without a good reason. For example, at my current job we want to be able to build some crates with older toolchains (at the very least 1.41, since it's the version packaged in Debian).

And even assuming we had synchronized MSRVs, I feel that the build badges are somewhat pointless. I don't think they have been useful to us even once, despite them taking a significant space in our READMEs. Also we don't even have cron jobs in our workflows, so the only place where things can break is in PRs.

@newpavlov newpavlov merged commit 5e01a42 into master Jul 13, 2021
@newpavlov newpavlov deleted the readme_msrv branch July 13, 2021 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants