Don't re-tag!

[dotlambda]

In #6903 @mgallien simply says

sorry that we had to change the tag after discovering issues in the initial tagged version

but makes no promises that this won't happen again in the future.
What's so difficult about creating a new tag if an issue with the old one is found? As @alerque points out in #6883

retagging releases is terrible practice making tons of work downstream and eroding trust too.

[mgallien]

I can see why you are not happy but are you sure you engage in an open and constructive discussion.
On my side, once I create a tag and see the release published on some distributions before the release is officially released by us is really problematic. I hope the conclusion will not be to make this happen behind closed doors just because you complained

So, as you can see, there are more things here and frankly I am not motivated to engage in that discussion starting by this tone.

[mgallien]

so I am not really sure I have willingness to engage in such discussions started in a such heated way

[dotlambda]

I don't think there's much to discuss.
I agree that we shouldn't have merged an updated before the official release but that doesn't make it okay to re-tag. I think it's common sense that re-tagging must never happen.

[dotlambda]

I suggested a change that will hopefully prevent premature updates in Nixpkgs: NixOS/nixpkgs#326355

[camilasan]

Since NixOS/nixpkgs#326355 was merged and since we have an internal issue open to improve this process, I am closing this discussion.