Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

⚡️ v0.42.0 RELEASE 🚀 #2808

Closed
20 of 47 tasks
achingbrain opened this issue Mar 2, 2020 · 4 comments
Closed
20 of 47 tasks

⚡️ v0.42.0 RELEASE 🚀 #2808

achingbrain opened this issue Mar 2, 2020 · 4 comments

Comments

@achingbrain
Copy link
Member

achingbrain commented Mar 2, 2020 •
edited
Loading

Bug fixes

🗺 What's left for release

🚢 Estimated shipping date

27th March

🔦 Highlights

  • Bug fixes

🏗 API Changes

  • ipfs.files.stat would return hamt-sharded-directory when statting a HAMT Shard, it now returns directory in line with go-IPFS.

✅ Release Checklist

  • Stage 0 - Automated Testing
  • Stage 1 - Internal Testing
    • Documentation
      • Ensure that README.md is up to date
        • Install section
        • API calls
        • Packages Listing
    • Network Testing:
      • test lab things - TBD
    • Infrastructure Testing:
      • TBD
  • Stage 2 - Community Dev Testing
    • Reach out to the IPFS early testers listed in docs/EARLY_TESTERS.md for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR.
    • Reach out on IRC for additional early testers.
  • Stage 3 - Community Prod Testing
    • Update js.ipfs.io examples to use the latest js-ipfs
    • Invite the IPFS early testers to deploy the release to part of their production infrastructure.
    • Invite the wider community (link to the release issue):
  • Stage 4 - Release
    • Take a snapshot of everyone that has contributed to this release (including its direct dependencies in IPFS, libp2p, IPLD and multiformats) using the js-ipfs-contributors module.
    • Publish to npm: 
      # In the root of the repo, run the following commands and follow the on-screen prompts:
npm run reset && npm i
npm run release
    • Publish a blog post to github.com/ipfs/blog (at minimum, a c&p of this release issue with all the highlights, API changes and thank yous)
    • Broadcasting (link to blog post)
    • Copy release notes to the GitHub Release description

❤️ Huge thank you to everyone that made this release possible

🙌🏽 Want to contribute?

Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:

⁉️ 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. We are also available at the #ipfs channel on Freenode.
@achingbrain achingbrain pinned this issue Mar 2, 2020
@ghost
Copy link

ghost commented Mar 3, 2020

Stage 2
"cite" Reach out to the IPFS early testers listed in docs/EARLY_TESTERS.md for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR."
docs/EARLY_TESTERS.md go to 404

@achingbrain
Copy link
Member Author

Nice catch, thanks - I've updated the links, they should point to the right places now.

@pcowgill pcowgill mentioned this issue Mar 5, 2020
Closed
@pcowgill
Copy link
Contributor

pcowgill commented Mar 9, 2020

When 0.42.0 of ipfs is released, is that when 42.0.1 of ipfs-http-client will be released? In other words, will releases be synchronized using lerna now? Will the versioning remain distinct between the child packages of this monorepo?

@achingbrain
Copy link
Member Author

achingbrain commented Mar 9, 2020 •
edited
Loading

Releases will most likely be synchronised but really it depends on what needs to be released and when.

We're also now publishing RCs on every green build of master, so you can get the latest & greatest by installing ipfs@next or ipfs-http-client@next, etc.

The versions will follow semver (as much as possible) using Conventional Commits, so they'll remain distinct and (hopefully) indicate the disruption a user will encounter on upgrading.

I want to get us to a point where we have steady, predictable releases, at least monthly or preferably completely automated, but please be patient with us while we're working out the kinks.

@achingbrain achingbrain unpinned this issue May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@achingbrain @pcowgill