Closed mirceaulinic closed 7 years ago
Same here, why merge into master without releasing?
Only to reduce the size of the PR when merged, as the testing framework migration is pretty big - but we can leave it open right now and commits pushed into develop
will be here as well.
Let's leave it open, when merging devel into master i mostly care about the tests passing anyway. The actual PR validates are done incrementally with each new addition anyway so no need of checking the base code yet again : )
Is this one ready for merge and release?
Mm not yet - I would like to fix #84 firstly and eventually try an implementation for #81 (if I can't do it today, I'll leave it for next week).
Let's merge #89 first.
Coverage increased (+2.06%) to 86.443% when pulling f88676ac6f46cea43ee3c24d89197acabafde512 on develop into dd1587d55fa9e7cba0a482c2e023793f45bb0ac2 on master.