Tracking issue for `cms` v0.3.0 release

Open
#2,430 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cryptography, release

Research direction

Start by reviewing the cms crate's release status and the dependency on a stable rsa crate. Determine whether the rsa-related functionality must remain for v0.3.0 or can be removed to unblock the release. Done means the release path is resolved and a stable cms v0.3.0 can be published.

Written by the indexing model from the issue text.

Description

This is a tracking issue for the final release of the cms crate, since we've had a few requests for crates that depend on it.

The current main blocker is a stable release of the rsa crate.

We could potentially remove the rsa-related functionality so we can cut a stable release earlier if need be.

Dominant language
Rust
Stars
338
Forks
188
Avg merge
4d 6h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RustCrypto/formats

All issues in RustCrypto/formats

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.