Hey Thibaut, I'm pretty sure I told you the contrary before (I was mistaken), but the version in lerna.json actually also needs to match up 0.2.0

Just to make sure:

• when this is merged, we do not create a new branch
• when we decide to release 0.2, we clone the head of master into a new branch beta
• right after, we bump master to 0.3.
• all subsequent code that goes into beta goes via backports.
• and from that point we just follow parity-ethereum's dev pattern

Ack, I bumped lerna.json I'll prepare the PR to bump to 0.3.

Hmm, I maybe wasn't clear. What I meant is that we keep 0.2.0 until we release beta. Only after the release do we do 0.3.0.

Ok that's also fine.