Replies: 3 comments
-
I think #145 is ready for merge. I believe the next "big" change (of course, it goes after the release) should be to stop using See #84 (comment) , #81 |
Beta Was this translation helpful? Give feedback.
-
I wouldn't hold off on anything to get the next version released, be it 1.1.1 or 1.2.0. Version numbers are free, there's nothing holding you to actually introducing some major non-breaking change in a minor version. Any "future" work can go into a next minor or major release as you noted. |
Beta Was this translation helpful? Give feedback.
-
1.2.0 has been just released. Let's move #145 to the next release - 1.3.0 or 2.0.0 (depending on its backward compatibility). |
Beta Was this translation helpful? Give feedback.
-
We have a number of things done & fixed since 1.1.0. It might be good to release it "soon". What important element we should wait for with 1.2.0?
#145 - ? - or it could wait for the next release @vlsi?
The next "bigger" version (not counting patch releases with bugfixes) would be 1.3.0 or 2.0.0 (depending on the compatibility changes with the required Java & Gradle versions or changes in the API).
Beta Was this translation helpful? Give feedback.
All reactions