Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release js-libp2p v1 #2104

Closed
7 of 8 tasks
SgtPooki opened this issue Oct 2, 2023 · 3 comments
Closed
7 of 8 tasks

release js-libp2p v1 #2104

SgtPooki opened this issue Oct 2, 2023 · 3 comments
Assignees

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Oct 2, 2023

discussed in https://pl-strflt.notion.site/Js-libp2p-v1-0-19d1a9724167469badaad4bf736cd7d6?pvs=4

Tasks

  1. maschad
  2. 0 of 9
    kind/discussion topic/docs
    maschad wemeetagain

For blog post:

  • Why now
  • Reminder of what all is in js-libp2p
  • Significant accomplishments over the last year
    • New connectivity
    • Transports
    • Monorepo
    • Cherry pick things from the release notes
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Oct 2, 2023
@achingbrain
Copy link
Member

I'd like to get the WebRTC stream fixes released before doing this, but @maschad can get started on the blog post before then.

I've added some PRs that will target v1 to the task list above.

@maschad maschad removed the need/triage Needs initial labeling and prioritization label Oct 3, 2023
@achingbrain
Copy link
Member

I have created a release-v1.0 branch that we can use to aggregate breaking changes ahead of release while not blocking bug fixes for 0.46.x.

On merge day I will rebase this on top of master and push locally to preserve individual PR commits.

cc @maschad @wemeetagain

@achingbrain achingbrain linked a pull request Nov 15, 2023 that will close this issue
@achingbrain
Copy link
Member

This has shipped!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants