752 - Make "marked as stale" more intelligent
----What steps will reproduce the problem?
1. Have a project where the most recent file is marked for WoW 2.4.3.
2. Edit the file to indicate compatibility for 3.0.2.
3. The project is still marked as "stale".
---- What is the expected output? What do you see instead?
The email I got telling me my project was now branded as "stale" indicated that this was because the most recent file was marked for compatibility only with WoW 2.4.3. This file is also compatible with WoW 3.0.2, but I did not mark it as such because it was still usable on what, at the time, was the current live version of WoW used by millions of players, and I did not wish to create confusion by marking my addon as "3.0.2".
I would expect that editing my file to indicate 3.0.2 compatibility would remove the "stale" flag. It did not, and now I either have to upload a useless non-update repack to get rid of it, or leave the rather insultingly worded tag on my addon.
"its latest file will likely not work with the most recent version of World of Warcraft." ... many addons WILL work with 3.0.2 without any changes, and most other addons will generate an error or two but still basically function. This tag is therefore misleading.
"The author may have abandoned it, or it may have outlived its usefulness." ... excuse me? You seriously think those are the ONLY reasons an addon might have been marked as "2.4.3"? You're telling thousands of users that my addon is either abandoned or not relevant to the new patch, simply because it's been a few hours and I haven't uploaded a repack to bump up the "last updated" date? Come on.
---- At what time and date (year, month, day) did you get this bug? (Include your timezone)
Tuesday, 14th October 2008, 4:09 PM PST
---- Please provide any additional information below.
I'm quite annoyed (even more than I usually am when I have to use CurseForge) that I now have to upload repacks of all of my addons to get rid of this desultory marker on my project pages, when simply changing the indicated version on the latest file SHOULD be enough.
- 2 comments
- 2 comments
Facts
- Last updated on
- 17 Feb 2009
- Reported on
- 14 Oct 2008
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- #2
XIU Tue, 06 Jan 2009 20:57:10Have the same problem with my add-on Wishlist. WowAce has a few new releases but Curse doesn't pick them up and it's still showing an old 2.4.3 build as the latest.
- #1
Phanx Tue, 14 Oct 2008 23:53:44Okay, I have uploaded "new" files for several of my projects. The files were approved. One of the projects (Speedometer) is STILL marked "stale". I give up. You want to tell users my addon is abandoned? Whatever. I don't care anymore.