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

V2.5.0 Release - πŸ“•βœ¨πŸ• Help from my friends #978

Closed
7 of 10 tasks
olizilla opened this issue Feb 26, 2019 · 9 comments
Closed
7 of 10 tasks

V2.5.0 Release - πŸ“•βœ¨πŸ• Help from my friends #978

olizilla opened this issue Feb 26, 2019 · 9 comments
Assignees

Comments

@olizilla
Copy link
Member

olizilla commented Feb 26, 2019

πŸ—Ίβœ¨ Features

πŸ›  Fixes and maintenance

@terichadbourne
Copy link

Some additional things I would hope to be able to do from this screen if possible:

  • Add nicknames next to CIDs (eg "Oli") so I know what the gobbledygook means.
  • Mark a few favorite/pinned peers that would then get surfaced to the top of my list if they're online

@hacdias
Copy link
Member

hacdias commented Aug 1, 2019

@olizilla since we now have the files in the wild thingy as a new feature, which I kind of consider major, shouldn't we use that for 2.5.0 and move the missing points here to 2.6.0?

@fsdiogo
Copy link
Contributor

fsdiogo commented Aug 5, 2019

@hacdias I'm going to release a new version of Web UI and write the release notes!

@hacdias
Copy link
Member

hacdias commented Aug 5, 2019

@fsdiogo okay! Please release it as 2.5.0 since it has a new feature πŸ˜ƒ

@fsdiogo
Copy link
Contributor

fsdiogo commented Aug 5, 2019

Done, release v2.5.0.

@fsdiogo fsdiogo closed this as completed Aug 5, 2019
@hacdias
Copy link
Member

hacdias commented Aug 5, 2019

Thank you!

@hacdias hacdias unpinned this issue Aug 5, 2019
@lidel
Copy link
Member

lidel commented Aug 13, 2019

Folks, was go-ipfs skipped on purpose?
It seems that go-ipfs 0.4.22 shipped with old webui (v2.4.4), which postpones ipfs/ipfs-companion#736 till the next release :(

Perhaps adding an explicit checklist to each release issue would help?

@hacdias
Copy link
Member

hacdias commented Aug 13, 2019

@lidel that was definitely a mistake... :'(

@lidel
Copy link
Member

lidel commented Aug 14, 2019

πŸ™ˆ I see v2.6.0 has a checklist to ensure we don't miss this again, thanks for adding it! πŸ‘ :)

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

No branches or pull requests

5 participants