@dchetelat yes that's normal, I forgot to merge #212 before releasing v0.7.0
The plan of action is the following:
we fast-forward master on dev (this PR), so that master is synced with the latest stable release, v0.7.0
we merge #212 into dev
we release a minor version v0.7.1 from dev
again, we fast-forward master on dev, so that master is synced with the latest stable release, v0.7.1
@AntoinePrv @dchetelat how does that sound ?
Ideally I would have done 1. right after I released v0.7.0, but I had to wait for one of you to approve the review (the PR was locked). This is a bit annoying, as while we are waiting the stable doc is not synced properly with the latest release @AntoinePrv do you think there is a way around it ?
@dchetelat yes that's normal, I forgot to merge #212 before releasing v0.7.0
The plan of action is the following:
masterondev(this PR), so thatmasteris synced with the latest stable release,v0.7.0devv0.7.1fromdevmasterondev, so thatmasteris synced with the latest stable release,v0.7.1@AntoinePrv @dchetelat how does that sound ?
Ideally I would have done 1. right after I released v0.7.0, but I had to wait for one of you to approve the review (the PR was locked). This is a bit annoying, as while we are waiting the
stabledoc is not synced properly with the latest release @AntoinePrv do you think there is a way around it ?Best, Maxime