Burak Yigit Kaya

I've always thought about this but can't make the decision myself as I'm not familiar why we set it up this way in the first place. Deferring to @asottile-sentry

It is fixable (at least to me), here's my reasoning: >the bump script has two required positional arguments (old version, new version) and passing nonsense is a breaking change Not...

>I assume you mean to the beginning of the history? HEAD is the current revision Up to `HEAD` from beginning. The entire commit history in short.

>I'd rather we fix this properly and deprecate the 2-arg release bump script and make a bump-version-v2.sh or whatever Why though? Having the old version available is definitely useful and...

@asottile-sentry I cannot justify the change you are asking for from a cost benefit standpoint. Making a deprecation for all existing projects, forcing an analysis and migration with a way...

@aldy505 >Any reason why you didn't use SeaweedFS per what you said yesterday? Well I started with that and realized 3 things: 1. It really is not geared towards single-node...

>@BYK Do you remember why we didn't use MinIO? Was it about licensing issue? Both licensing and reported performance and scalability issues reported by others.

@aldy505 >We should have a proper migration path for existing installs Don't think we have this either?

I'd say default for fresh installs. And since we prompt people for existing installs, it should be fine?

@ministicraft thanks for asking about this! Unfortunately Seer became closed source recently and there's a PR to update the docs accordingly: https://github.com/getsentry/sentry-docs/pull/14204/files