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

JS IPFS 0.38 release handover #4

Closed
5 of 6 tasks
alanshaw opened this issue Sep 2, 2019 · 4 comments
Closed
5 of 6 tasks

JS IPFS 0.38 release handover #4

alanshaw opened this issue Sep 2, 2019 · 4 comments
Assignees

Comments

@alanshaw
Copy link
Member

alanshaw commented Sep 2, 2019

Friends, now that the js-ipfs release process improvements are in the pipeline I can start making arrangements for when I'll be unavailable: 1 month from ~next week.

If we'd started the 0.38 release at the right time the estimated date for shipping would be 17th September. If we're a couple of weeks delayed then I'd still not be back in time to do the release.

Off the top of my head the following needs to happen:

  • Finalise feature list for 0.38 release. I've listed a few of items I think we should definitely include and put a (?) suffix on items I think we could include but might need some more consideration.
  • Choose a volunteer release manager(s) for the 0.38 release - @achingbrain has already said he can help, it might be cool to have a duo? Is anyone else interested in pairing up?
  • Ensure release manager(s) have write access to js-ipfs, js-ipfs-http-client and interface-js-ipfs-core
  • Release manager(s) need to enable 2FA on npm
  • Add release manager(s) as collaborators on npm for ipfs, ipfs-http-client and interface-ipfs-core
  • Walk through the process with the release manager(s)
  • ...I missed a thing? Please tell me!

cc @momack

@hugomrdias
Copy link
Member

I'm also available to help with the release.

@alanshaw
Copy link
Member Author

alanshaw commented Sep 4, 2019

Not explicitly covered above but the release managers on this occasion would also be responsible for day to day lead maintainer duties up to the release but also afterwards until I return!

I've added @achingbrain and @hugomrdias as collaborators on npm, you both have 2FA setup already (good job!) and you're both in the repos-javascript team so you should have write access to the relevant repos.

@jimpick
Copy link

jimpick commented Sep 5, 2019

I'm happy to help out as well! I've only dabbled a bit in the codebase so far though...

@alanshaw
Copy link
Member Author

Thanks @achingbrain and @hugomrdias for handling everything while I was away! I came back to it all in a better state than I left it ❤️

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

No branches or pull requests

9 participants