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

• 

  • #4

  Ackis Mon, 19 Jan 2009 18:42:03

  Yah I'm trying to keep tickets cleaned up, I want the mark as duplicate to work a bit better tbh, but that's how it is right now.

• 

  • #3

  Phanx Fri, 16 Jan 2009 03:55:15

  I'd posted a new ticket recently, having forgotten about this one since it was ignored for so long, and mine was closed as a Duplicate, so I'll repost it here as a comment.

  Currently, when a file marked "beta" syndicates to Curse.com, it does not affect the "last updated" date, it does not notify users who've added the project to their favorites list that there is an update, it continues to give users who click the big fat Download button the older "release" version, and it gives no "above the fold" indication that any beta versions are available.

  For example, I've just finished rewriting one of my addons from scratch, and while the functional bits are all done, the GUI isn't done yet. Technically, I feel this should be labeled as a beta, since it is incomplete, but I also feel that it is ready for general usage, especially since the previous release version is crippled by a fundamental inability to properly support certain WoW 3.0 changes (in fact this is exactly why I rewrote it) and should not be used by anybody anymore. While I would love to get the GUI finished, the reality is simply that I do not have unlimited time to code. In this situation, with the site's current functionality, I can either mark new versions as "release" even though they shouldn't be, or I can mark them as "beta" and then answer dozens of PMs, emails, and tickets asking me to fix bugs that exist in the last "release" version because nobody has any idea that there are newer versions available.

  WoWInterface handles this situation by adding a visible "Beta" tab at the top of the page, where it is easily and quickly seen by users.

  An even better solution would be to add a project-level preference for allowing "beta" files to be the default download for the project. Then, users wouldn't even have to look (which is probably asking too much given that most of them don't read the bold text at the top of my description telling them to scroll down for the betas), just mindlessly click the Download button.

  For those voting this down, keep in mind that this would be an option at the project level. If you are never in a situation where it is appropriate for your project's default download to be a beta file, simply don't enable the option.

• 

  • #2

  Kane Sun, 19 Oct 2008 16:49:42

  Agreed. I suggested the same in my ticket yesterday

• 

  • #1

  Phanx Thu, 18 Sep 2008 04:16:38

  Agreed. Currently, I never mark a version as "beta" because of this, unless EVERY version is a "beta".