List view
See https://github.com/orgs/ipfs/projects/16/views/7?filterQuery=iteration%3A%22go-ipfs+0.14%22 for all the items on the board.
Due by July 22, 2022•12/12 issues closedhttps://github.com/ipfs/go-ipfs/issues/8640
Due by April 29, 2022•54/54 issues closed- Due by July 23, 2021•3/3 issues closed
https://github.com/ipfs/go-ipfs/issues/8344
Due by February 17, 2022•5/5 issues closedhttps://github.com/ipfs/go-ipfs/issues/8343
Due by December 9, 2021•24/24 issues closedhttps://github.com/ipfs/go-ipfs/issues/8176
Due by October 4, 2021•18/18 issues closed- Due by June 23, 2021•16/16 issues closed
- No due date•2/2 issues closed
https://blog.ipfs.io/2021-02-19-go-ipfs-0-8-0/
Due by February 20, 2021•2/2 issues closed- Due by September 15, 2020•6/6 issues closed
- Due by June 9, 2020•17/17 issues closed
- Due by April 28, 2020•11/11 issues closed
- No due date•1/1 issues closed
- No due date•1/1 issues closed
- No due date•2/2 issues closed
- No due date•27/27 issues closed
- No due date•29/35 issues closed
- No due date•9/9 issues closed
- No due date•23/23 issues closed
- Due by May 20, 2017•13/13 issues closed
- Due by April 7, 2017•14/14 issues closed
- Due by March 29, 2017•19/19 issues closed
- No due date•45/45 issues closed
Potential breaking changes. They need to be documented.
No due date- No due date•35/35 issues closed
- No due date•1/1 issues closed
- Due by December 5, 2016•15/17 issues closed
ipfs unixfs currently can't handle large directories. We need to shard directories after they get to a certain size.
Due by November 8, 2016•2/2 issues closedIpfs should strive not to kill peoples home internet connection. This milestone is for tracking router killer issues beyond the normal bandwidth problems.
Due by December 12, 2016•2/3 issues closedIPFS is decently fast, but its nowhere near where we want it. This milestore is to get us to speed things up a bit.
Due by January 8, 2017•4/5 issues closedWe want to significantly improve the experience developers have using ipfs. This includes making the codebase more approachable, making tutorials, and making our tooling as perfect as we can get it.
Due by January 2, 2017•1/2 issues closedA milestone for reducing resource consumption down to a reasonable level within a fixed time scale (Q4 2016)
Due by January 2, 2017•4/4 issues closed- Due by September 16, 2016•1/1 issues closed
This milestone's goal is to extract the gateway code into its own tool. This will facilitate the implementation of the Core API in go-ipfs. In the past months we've established a core set of commands that IPFS nodes can support. The JS implementation (js-ipfs and js-ipfs-api) is already compliant, and this milestone is all about starting to make the Go implementation (go-ipfs and go-ipfs-api) compliant. Check out https://github.com/ipfs/interface-ipfs-core
Due by October 31, 2016•6/7 issues closed- Due by August 31, 2016•17/17 issues closed
integration of the ipld data format into go-ipfs
Due by October 29, 2016•15/15 issues closedTasks that need to be completed for the go and javascript implementations to be able to communicate.
Due by August 26, 2016•6/6 issues closedVersion 0.4.5 of go-ipfs
Due by November 19, 2016•66/66 issues closed- Due by July 30, 2016•10/10 issues closed
- Due by July 5, 2016•43/43 issues closed
Final release before 0.4.0
Due by December 10, 2015•3/3 issues closed- No due date•4/4 issues closed
- Due by October 8, 2015•5/5 issues closed
Ipfs 0.3.6 release.
No due date•41/41 issues closedThis milestone covers everything thats going to make it into the 0.4.0 release. 0.4.0 will be a fairly major release, bringing with it large protocol changes and perf improvements, as well as a change in the way ipfs data is stored and managed.
No due date•6/7 issues closedThis milestone covers a whole bunch of fixes for daemon things.
No due date•5/8 issues closed- No due date•9/10 issues closed
This Milestone upgrades the repo.
No due date•10/10 issues closedThe new framework is merged into master in the `cmd/ipfs2` directory. Right now, we refer to the new command binary as `ipfs2`. However, as soon as this milestone is reached, we will move it into the `cmd/ipfs` directory as `ipfs`. The files that comprise old command binary will be deleted. This milestone tracks our transition.
Due by November 17, 2014•5/5 issues closedThis milestone tracks the progress of PR #263 (merging the new commands framework). This branch will be merged into master once the issues herein have been resolved. https://github.com/jbenet/go-ipfs/pull/263 Comprehensive checklist is kept in a Google Sheet: https://docs.google.com/a/perfmode.com/spreadsheets/d/1XgSDZGTSIrgdO48lLzUKLYTzZHk-ggW9RMJm2U-nrLs/edit#gid=0
Due by November 13, 2014•21/21 issues closed