-
Notifications
You must be signed in to change notification settings - Fork 230
About release version scheme #2194
Comments
I am in agreement with you regarding the version number and do wish we had put more thought into it before the re-release a few months ago. I was thinking about this while doing the last release, so I'm grateful you opened this issue for discussion. Within a release or two, SQL3 should be fully integrated into the UI and likely made the default query method. Technically, a major version bump at that time would make sense due to the API becoming incompatible with previous releases. As it stands right now, these versions still support the older calling methods... |
No worries, trying to help here. :)
The project renaming should already granted the major release (the artifact got name change?), and regarding the API version stuff, I think either it would be managed separately (I see somebody are doing that), or, we can just do another major version bump regarding the incompatibility part. Let me know if that makes sense. |
@chenrui333 we've done a new release and have changed the version to match internal versions of the binaries. Please let me know your thoughts on this and anything we might need to do to assist you with the homebrew formula. |
Closing this as the versions are now updated! @chenrui333 be sure to join our Discord if you need anything! |
I know
featurebase
is derived frompilosa
, but the latest release forpilosa
was 1.4.1, and it looks like the new community version forfeaturebase
is withv1.0.0-community
? Just curious, why not just usev2.0.0
instead?Asking because I am thinking to revive the homebrew formula, but the version scheme really bothers me. Thanks!
The text was updated successfully, but these errors were encountered: