784 - Doomed after accidentally tagging a 'release'

What steps will reproduce the problem?
1. Develop your addon
2. Tag a beta version accidentally with the name "v0.1"
3. Realize that your addon's release type is 'release'
4. Delete the tag from the repository
5. Tag a beta version with the name "v0.1beta";

What is the expected output? What do you see instead?

I would expect that the accidentally released version is not available for download after I delete the tag. Now I see that both v0.1 and v0.1beta are listed in curse. But there is worse, the current version is v0.1 (release) even though v0.1beta was released later. That means, if I release new beta versions in the future, the v0.1 will always be the current version. That is unacceptable.

At what time and date (year, month, day) did you get this bug? (Include your timezone)
19:45 GMT +1
18/10/2008

User	When	Change
Kane	Sun, 19 Oct 2008 20:38:25	Changed status from New to Invalid
Kane	Sat, 18 Oct 2008 17:49:09	Create

You must login to post a comment. Don't have an account? Register to get one!

5 comments

- Reply
- #5
Kane Sun, 19 Oct 2008 20:38:10
Thanks. Deleting the file solved the problem. Sadly I could only find out that I could delete I file after seeing your suggestion.
(And now I can't find out how to change the status of my ticket. Let's see if abandon does the trick..)
- Reply
- #4
anmoch Sun, 19 Oct 2008 18:31:10
Just delete your release file.
The beta/release distinction isn't there to make you feel good. It prevents users from installing betas automatically via updaters. Any (big enough to need it) project will usually tag a few betas before tagging a release, then start over with the next beta cycle.
- Reply
- #3
Arrowmaster Sun, 19 Oct 2008 17:31:50
You can delete files, so do it.
- Reply
- #2
Kane Sun, 19 Oct 2008 16:15:54
The alternatives are actually pretty simple. You should be able to choose the current version. Or you should be able to remove a version because you may have added them unintentionally.
Why would anyone publish a beta version after publishing a release version? One of the cases that I can think of: The first release was published accidentally. And after this accident, you can never ever fix this problem. You can never state that the 'release version' was unintentional and continue with your beta versions. Can you?
The distinguishment between release and beta is another topic. But to summarize, beta version are at testing phase which means they may be unstable. Release versions are supposed to be stable (to some extend).
- Reply
- #1
anmoch Sun, 19 Oct 2008 08:57:28
You say "That is unacceptable", but have you considered the alternative? It would be to always default the download to the newest tagged version, beta or release.
Do you really want every user out there to run beta?
More to the point, why distinguish between beta and release if they're both pushed out to everyone?