Skip to content
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.

Go-IPFS 0.5 release #470

Closed
johnnymatthews opened this issue Mar 18, 2020 · 9 comments
Closed

Go-IPFS 0.5 release #470

johnnymatthews opened this issue Mar 18, 2020 · 9 comments
Assignees
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks Epic kind/enhancement A net-new feature or improvement to an existing feature P0 Critical: Tackled by core team ASAP status/in-progress In progress topic/docs Documentation

Comments

@johnnymatthews
Copy link
Contributor

johnnymatthews commented Mar 18, 2020

This is the epic issue for the Go-IPFS 0.5 release. Closing the following issues closes this epic: #471, #472, #473, #474.

This 0.5 release is slated to be the biggest release since the Go-IPFS project started. See the Road to 0.5 issue in ipfs/go-ipfs for more details regarding the release.

With the release of Go-IPFS 0.5 coming up, we need to create a place for major update docs to sit. Below is a solution that should work just fine, but can be altered in the future if needed. I'd rahter not spend too much time discussing and deliberating over this layout since 0.5 is due to be released in early April, and so we need this out the door by then.

Install IPFS    <--- Main dropdown label
    Desktop    <--- Page
    Browser
    Terminal
Updates    <--- Main dropdown label
    Go-IPFS 0.5 release    <--- Bold label
        Overview    <--- Page
        Update procedure
        Features
            IPNS    <--- H2 in page
            IPFS subdomain gateway
            Bitswap
            Data stores (Badger)
            ...
        Fixes
        Troubleshooting
            Node discoverability

Here is an example screenshot from the ipfs-docs-v2 beta to demonstrate the labeling system:

label-header-example

@johnnymatthews johnnymatthews added Epic topic/docs Documentation dif/hard Having worked on the specific codebase is important docs-ipfs P0 Critical: Tackled by core team ASAP labels Mar 18, 2020
@johnnymatthews johnnymatthews self-assigned this Mar 18, 2020
@johnnymatthews johnnymatthews pinned this issue Mar 18, 2020
@johnnymatthews
Copy link
Contributor Author

See ipfs/ipfs-docs-v2:go-ipfs-0.5 branch.

@johnnymatthews
Copy link
Contributor Author

Here's a screen cap the sidebar.

Annotation 2020-03-19 131501

Having Go-IPFS 0.5 one of the bolded labels, this gives us room to expand for other major releases like JS-IPFS, or Rust when that comes out.

@jessicaschilling
Copy link
Contributor

Awesome 😊
Would "Release notes" make more sense than "Updates"?

@johnnymatthews
Copy link
Contributor Author

Yeah, although it's not all strictly release notes. Releases might work better.

@jessicaschilling
Copy link
Contributor

"Recent releases"?
Just to make it really clear that it's not somewhere you can get ALL the releases ... that's the dist.ipfs.io site.

@johnnymatthews
Copy link
Contributor Author

Good point. Yeah ok, let's go with Recent releases.

@johnnymatthews
Copy link
Contributor Author

As requested by @momack2, here's a screenshot of what the Recent releases section looks like now:

Untitled

@momack2
Copy link
Contributor

momack2 commented Apr 8, 2020

Awesome! Thank you.

@johnnymatthews johnnymatthews added effort/weeks Estimated to take multiple weeks dif/expert Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature P0 Critical: Tackled by core team ASAP status/in-progress In progress topic/docs Documentation and removed Size: XL P0 Critical: Tackled by core team ASAP dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks topic/docs Documentation labels Apr 17, 2020
@johnnymatthews
Copy link
Contributor Author

Go-IPFS 0.5 released!

@johnnymatthews johnnymatthews unpinned this issue Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks Epic kind/enhancement A net-new feature or improvement to an existing feature P0 Critical: Tackled by core team ASAP status/in-progress In progress topic/docs Documentation
Projects
None yet
Development

No branches or pull requests

3 participants