Version constraints
Closed this issue · 5 comments
lassepe commented
Shouldn't the current version (0.3.0) have POMDPs v0.8 as a lower bound because it want's to use the DDNStructucture type which does not exist in v0.7.3?
MaximeBouton commented
POMDPs v0.7.3 does export DDNStructure I think.
lassepe commented
Oh never mind. I got this wrong. I was looking at the master, not v0.7.3. Thank you @MaximeBouton!
MaximeBouton commented
Actually, why is v0.7.3 not merged to master? @zsunberg
zsunberg commented
I thought it made more sense to have v0.8 merge into master and any future
0.7 releases come from the version-0.7 branch. The commits for version
0.7.3 branch away from the version 0.8 commits, so there would be a weird
merge if we merged 0.7.3 into master before 0.8. I thought 0.8 seemed more
like the trunk.
…On Tue, Sep 17, 2019 at 6:07 PM Maxime ***@***.***> wrote:
Actually, why is v0.7.3 not merged to master? @zsunberg
<https://github.com/zsunberg>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=ABALI25M7AOCRH5U5LT4ZXTQKF5MHA5CNFSM4IXXH4R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD66OZQY#issuecomment-532475075>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABALI25N7OGIVNNL2WB7CU3QKF5MHANCNFSM4IXXH4RQ>
.
MaximeBouton commented
Ok I did not realize there would be more 0.7.3 versions but I think it makes sense.