v0.6.0 release cycle

Why not releasing next week

Next week, all major and breaking changes will be merged
If we would release by Thursday (as planned), there would be little time to:
- Prepare the community
- Integrate postage stamps in bee-js / our docs
There are unresolved problems with our current network (it doesn't work). There are strong pointers to the problems (made possible by the community)
- Not resolving these issues by the next release will disappoint our community
- Not resolving these will deprive us from further testing by the community
- Not resolving these will make it less attractive for node operators to update
- Not resolving these by the next release will make it uncertain at least till the next release whether we actually fixed our stuff
known culprits are:
- Wrongly conclude that I am the closest node when building up Kademlia
- push sync timeout
  - https://github.com/ethersphere/bee/issues/1423
  - https://github.com/ethersphere/bee/issues/1044
- Not being able to handle peers with insufficient paymenth threshold (Dappnode peers cause havoc in our existing network)
- dynamically increase open file limit

Some issues might already be resolved, or improved.
It is going to be hard anyways to validate if our fixes improve stuff. The reason for this is because current master is incompatible with the latest release. Starting a cluster with public testers on staging is not guaranteed to replicate issues we currently see on the public cluster

We merge everything to master next week
We do a public testing session on Wednesday, announce the release of all this in two weeks
We start a sprint where we actively work on restoring the working of our network
- Take bug reports as pointers,
- actively investigate ourselves what is happening
- Ask community members to run nodes on staging
- Open standup for all people who work on bug fixes, validate fixes, investigate issues