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

Add 0.4.21 CHANGELOG #6372

Merged
merged 8 commits into from
May 29, 2019
Merged

Add 0.4.21 CHANGELOG #6372

merged 8 commits into from
May 29, 2019

Conversation

Kubuxu
Copy link
Member

@Kubuxu Kubuxu commented May 23, 2019

WIP. Please either add or mention in comments what should be featured.

@Kubuxu
Copy link
Member Author

Kubuxu commented May 23, 2019

Should we clean up dependency changelog?

@Kubuxu Kubuxu mentioned this pull request May 23, 2019
@Stebalien
Copy link
Member

Should we clean up dependency changelog?

Probably. Really, I wouldn't print out the version changes, that doesn't say much. Instead, I'd print the actual change log (commit messages) from each dep in one of our orgs (multiformats, ipfs, ipld, libp2p, etc.).

Going through that also helps flesh out the features/changes.

@Kubuxu
Copy link
Member Author

Kubuxu commented May 23, 2019

I can write that, but this will be even more noise.
We for sure don't want to include git changelogs for the whole libp2p ecosystem in our changelog.

@djdv
Copy link
Contributor

djdv commented May 23, 2019

minor change (may or may not be worth mentioning) in: #6277

We're now base64 encoding values returned by dht get when encoding them into JSON

Previously these where byte slices directly cast as strings, which could produce invalid values/output.
Now the binary values are encoded.

@Stebalien
Copy link
Member

We for sure don't want to include git changelogs for the whole libp2p ecosystem in our changelog.

It's actually quite useful as we benefit from all of those changes. We don't have to include them but I wouldn't include the version changes regardless.

Take a look at the changelogs from the last few releases.

minor change (may or may not be worth mentioning) in: #6277

We should definitely mention that as a breaking change.

CHANGELOG.md Outdated
go versions during builds.


(please point out what should be featured, doesn't have to be go-ipfs).
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we pull the list of contributors like Alan did in the most recent js-ipfs release? https://github.com/ipfs/js-ipfs/releases/tag/v0.36.0

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated
- reprovider: Use goprocess ([ipfs/go-ipfs#6248](https://github.com/ipfs/go-ipfs/pull/6248))
- add: Fix adding multiple files ([ipfs/go-ipfs#6255](https://github.com/ipfs/go-ipfs/pull/6255))
- dep: update libp2p, dht, peerstore, swarm, secio ([ipfs/go-ipfs#6257](https://github.com/ipfs/go-ipfs/pull/6257))
- Fix AutoNAT service for private network ([ipfs/go-ipfs#6251](https://github.com/ipfs/go-ipfs/pull/6251))
Copy link
Contributor

Choose a reason for hiding this comment

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

is this notable?

Copy link
Member

Choose a reason for hiding this comment

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

It's unlikely to affect many users.

CHANGELOG.md Outdated
- docs: fix Routing section ([ipfs/go-ipfs#6309](https://github.com/ipfs/go-ipfs/pull/6309))
- fix(Dockerfile): Allow ipfs mount in Docker container ([ipfs/go-ipfs#5560](https://github.com/ipfs/go-ipfs/pull/5560))
- test(coreapi): use a thread-safe datastore everywhere ([ipfs/go-ipfs#6222](https://github.com/ipfs/go-ipfs/pull/6222))
- ping: fix a bunch of issues ([ipfs/go-ipfs#6312](https://github.com/ipfs/go-ipfs/pull/6312))
Copy link
Contributor

Choose a reason for hiding this comment

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

any of these worth calling out?

Copy link
Member

Choose a reason for hiding this comment

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

Done.

CHANGELOG.md Outdated
- doc: remove out of date documentation ([ipfs/go-ipfs#6345](https://github.com/ipfs/go-ipfs/pull/6345))
- core: Use correct default for connmgr lowWater ([ipfs/go-ipfs#6352](https://github.com/ipfs/go-ipfs/pull/6352))
- fix vendoring dependencies when building the source tarball ([ipfs/go-ipfs#6349](https://github.com/ipfs/go-ipfs/pull/6349))
- feat: improve errors when a path fails to parse ([ipfs/go-ipfs#6346](https://github.com/ipfs/go-ipfs/pull/6346))
Copy link
Contributor

Choose a reason for hiding this comment

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

yay for better errors?

Copy link
Member

Choose a reason for hiding this comment

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

Done.

Kubuxu and others added 5 commits May 28, 2019 04:05
@Stebalien
Copy link
Member

I've filled out the release notes and added a recursive changelog.

@Stebalien
Copy link
Member

cc @ipfs/wg-go-core please review.

CHANGELOG.md Outdated Show resolved Hide resolved
@eingenito
Copy link
Contributor

@Stebalien Should we mention the intention to default to dhtclient routing in a future release?

@Stebalien
Copy link
Member

@Stebalien Should we mention the intention to default to dhtclient routing in a future release?

Thanks for the reminder. Yes!

Co-Authored-By: Dominic Della Valle <[email protected]>

#### Human Readable Numbers

The `ipfs bitswap stat` and and `ipfs object stat` commands now support a
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The `ipfs bitswap stat` and and `ipfs object stat` commands now support a
The `ipfs bitswap stat` and `ipfs object stat` commands now support a

@Stebalien
Copy link
Member

@Stebalien Should we mention the intention to default to dhtclient routing in a future release?

Ugh. It looks like configs specify "dht" by default, not "". We'd have to reinterpret that to change the default for existing nodes.

We can still make it the default for future nodes but that doesn't really require an announcement this release.

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@Stebalien
Copy link
Member

We can clean these up post-release if necessary. Let's get this out the door.

@Stebalien Stebalien merged commit 6cd273f into master May 29, 2019
@Stebalien Stebalien deleted the feat/0.4.21-releaselog branch May 29, 2019 22:23
@Stebalien Stebalien restored the feat/0.4.21-releaselog branch May 30, 2019 22:35
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

Successfully merging this pull request may close these issues.

6 participants