Skip to content

docs: add release post for [email protected] #420

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 12 commits into from
Jun 1, 2022
Merged

docs: add release post for [email protected] #420

merged 12 commits into from
Jun 1, 2022

Conversation

achingbrain
Copy link
Member

Alex Potsides updated src/_blog/releasenotes.md

Alex Potsides added 3 commits May 27, 2022 15:28
Update from Forestry.io
0262e01 
Alex Potsides updated src/_blog/releasenotes.md
Update from Forestry.io
bd3ee06 
Alex Potsides updated src/_blog/releasenotes.md
Update from Forestry.io
f5ef1f7 
Alex Potsides created src/_blog/js-ipfs-0.63.0-esm-libp2p-0.37.x-and-lightweight-peerids.md
@achingbrain achingbrain requested a review from BigLep May 30, 2022 19:36
BigLep
BigLep suggested changes May 31, 2022
View reviewed changes
Copy link
Contributor

@BigLep BigLep left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff - thanks for getting this out! Initial set of feedback. Will look again.

src/_blog/js-ipfs-0.63.0-esm-libp2p-0.37.x-and-lightweight-peerids.md Outdated

- Check the issues with the `help wanted` label in the [js-IPFS repo](https://github.com/ipfs/js-ipfs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)
- Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute: https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good idea, but we don't have a venue for this currently.

src/_blog/js-ipfs-0.63.0-esm-libp2p-0.37.x-and-lightweight-peerids.md Outdated
- Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute: https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
- Join the discussion at https://discuss.ipfs.io/ and help users finding their answers.
- Join the [🚀 IPFS Core Implementations Weekly Sync 🛰](https://github.com/ipfs/team-mgmt/issues/992) and be part of the action!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similarly should be removed right?

src/_blog/js-ipfs-0.63.0-esm-libp2p-0.37.x-and-lightweight-peerids.md Outdated

# ⁉️ Do you have questions?

The best place to ask your questions about IPFS, how it works, and what you can do with it is at [discuss.ipfs.io](https://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Freenode isn't accurate.

This needs updating as well, but I think it would be ideal to add a layer of indirection here. Lets just link to something like https://github.com/ipfs/ipfs and we keep that updated.

src/_blog/js-ipfs-0.63.0-esm-libp2p-0.37.x-and-lightweight-peerids.md Outdated

> switches to ESM only, upgrades to [email protected] and brings lightweight PeerIds

`[email protected]` is powering through the stratosphere along with many small bug fixes and performance improvements!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a key thing here is that this release was really about setting up a first foundation to "launch" from.

Maybe something like

[email protected] is rocketing forward with major improvements to its foundations along with many small bug fixes and performance improvements!

@BigLep
Copy link
Contributor

BigLep commented May 31, 2022 •
edited
Loading

Some other high-level thoughts before I get pulled into other things today:

  1. In general, I think we should add indirection. Have the blog entry link to a landing page that that describes where the latest roadmap is or communication channels. For example, our roadmap link is likely to change. Rather than hardcoding to a specific project board, we link to the doc which points to where it is.
  2. It's not clear to me where we put the contributor stats. In this case it looks like we put it in the blog entry but not the release page or changelog. I would have thought we'd do the opposite (and I believe that is what go-ipfs does as well). Regardless, I think we need to document what the release process is so this is understood and can be followed by others: ipfs/CHANGELOG.md is out of order js-ipfs#4119
  3. Is there a way to easily see the rendered form on the blog?
  4. Does marketing like to be engaged before we push?

@emilymvaughan
Update from Forestry.io
c5457fa 
[email protected] created src/_blog/welcome-to-ipfs-news-178.md
@emilymvaughan
Update from Forestry.io
dc4cfe4 
[email protected] created src/assets/171309710-5d63b147-353f-48fb-a272-177ca8f0d799.png
@emilymvaughan
Update from Forestry.io
48d2d10 
[email protected] updated src/_blog/welcome-to-ipfs-news-178.md
BigLep
BigLep reviewed Jun 1, 2022
View reviewed changes
Copy link
Contributor

@BigLep BigLep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional comments on the js-ipfs PR.

BigLep and others added 4 commits June 1, 2022 14:31
@BigLep
Apply suggestions from code review
5d0607b
@BigLep
Incorporating more code review comments
57d2404 
Removing discussion of roadmap and what's next since they weren't accurate.  The goal is to unblock shipping this blog entry.
@BigLep
Apply suggestions from code review
c3c77c1
@BigLep
Removing "What's next" section
bde1968
@BigLep BigLep self-requested a review June 1, 2022 21:39
BigLep
BigLep approved these changes Jun 1, 2022
View reviewed changes
Copy link
Contributor

@BigLep BigLep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed https://ipfs-blog-staging.on.fleek.co/ and the js-ipfs and js-libp2p items look good to me.

@emilymvaughan
Update from Forestry.io
a5b69d0 
[email protected] updated src/_blog/welcome-to-ipfs-news-178.md
@emilymvaughan emilymvaughan merged commit 7d82006 into main Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BigLep BigLep BigLep approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@achingbrain @BigLep @emilymvaughan