0.15 release planning

Open
#418 3 comments 0 reactions 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
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
release

Research direction

Start by reviewing issues #394, #409, #413, #414, and #446 to understand the planned 0.15 scope. Decide whether an extension trait for user-provided extensions belongs in that release and document the agreed design and work items; completion is a settled release plan rather than an identified code change.

Written by the indexing model from the issue text.

Description

  • #394
  • #409
  • #413
  • #414
  • #446

Maybe we should have some kind of extension trait to allow people to bring their own extensions?

Dominant language
Rust
Stars
516
Forks
160
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 rustls/rcgen

All issues in rustls/rcgen

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.