You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last released version, 0.9.0, is coming up on its second birthday (:cake:).
I think it would be good to tag a new release with the fixes to master that have been made since, assuming there are no breaking bugs in those.
I also think that the unique2 branch should see some form of release, again with the condition that there are no breaking bugs. I also think that merging unique2 into master would be reasonable, or is there a reason to keep it from being the official new version?
Regarding version numbers, I think the most reasonable would be to release the current changes to master as 1.0.0 and unique2 as version 2.0.0.
If you agree, I could whip up some pull requests doing these things.
Thoughts?
The text was updated successfully, but these errors were encountered:
The last released version,
0.9.0
, is coming up on its second birthday (:cake:).I think it would be good to tag a new release with the fixes to
master
that have been made since, assuming there are no breaking bugs in those.I also think that the
unique2
branch should see some form of release, again with the condition that there are no breaking bugs. I also think that mergingunique2
intomaster
would be reasonable, or is there a reason to keep it from being the official new version?Regarding version numbers, I think the most reasonable would be to release the current changes to
master
as1.0.0
andunique2
as version2.0.0
.If you agree, I could whip up some pull requests doing these things.
Thoughts?
The text was updated successfully, but these errors were encountered: