Seriously, stop. An addon not getting an update for 90 days absolutely does not mean it's abandoned. I still have at least one addon that's working flawlessly with no updates since the Burning Crusade. It's incredibly annoying to have to go fix my addon pages every time you guys wrongly plaster a giant "THIS ADDON IS ABANDONED" banner all over them and make them disappear from Curse.com and the Curse Client. If I'm not going to support an addon anymore, I'll flag it as abandoned myself, or just delete it.
At present it's been less than 24 hours since the patch went live, and already you flagged EVERY SINGLE ONE of my several dozen addons as abandoned. F*** off. Seriously.
I'm not sure how the automated system works when flagging projects, but there is a way to beat the system: mark your projects as "mature" and boom, never see that message again!
If an addon gets marked as inactive, and I then check in and tag a new release, does its status ever get changed back automatically? So far, doesn't seem to be happening.
If not, the whole thing seems like a major problem for those of us who maintain addons where the original authors/managers aren't really around anymore. (Although maybe inactive doesn't really mean much, since it doesn't seem to be stopping it from being available on Curse...)
I think you need to set it back to Release in the project settings.
If the original author left, and noone has officially managed to take the project over (ie. by getting permission from the author and getting manager status on the project), it does kinda mean that the project at least is somewhat inactive.
I think the inactive pass was too aggressive this time, as it usually only does its thing after months of inactivity and no current version, and not one day after the expansion release, but what can you do, just update them and set them back to release.
Mature is not a valid flag for addons, its only to be used on libraries.
Well, auto-marking my addon as inactive/abandoned if I don't post an update for 90 days is unacceptable, so I'm going to continue marking my mature addons as "Mature". There's just no logical reason to force me to waste everyone's time (especially my own) by posting fake updates for 40+ addons every 90 days. :mad:
Well, in my case, I have maintainer access, but not manager access. So I cannot change the status back.
Use the microscopic "report" icon in the bottom right corner of the project page to ask a moderator to bump you up to Project Manager. If you're already listed on the project and actively maintaining it, and the manager is AWOL, there's no reason not to promote you.
Well, auto-marking my addon as inactive/abandoned if I don't post an update for 90 days is unacceptable, so I'm going to continue marking my mature addons as "Mature". There's just no logical reason to force me to waste everyone's time (especially my own) by posting fake updates for 40+ addons every 90 days. :mad:
And Torhal is going to be unflagging them again.. He likes that part of his job! :D
As long as they have a file thats for the current version of WoW, they shouldn't get flagged. None of mine did, until the day 6.0 was set as the primary WoW version (where the over aggressive comes in)
Well, somehow the addon (Scorchio was the one in question) got changed back to Release status from Inactive. Don't think it was the manager, as he hasn't logged into WowAce since July. Dunno if it was someone reading this thread (thanks if so), or if it's been automated?
This is indeed annoying. The version check seems not be related to the Interface version in the TOC which is checked by the WoW client, but rather to some maintenance patch version number. At least this should be changed.
Yeah, that looks like it's not related to any version numbers -- they automatically mark your addon as "Inactive, might not work anymore" if you don't post an update for 90 days. I've started marking many of my addons as "Mature" even though Nev says that's "only to be used on libraries", because insisting I post a fake update every 3 months to keep my addon visible to users (inactive addons don't show up in the Curse client unless you already have them installed, and might not show up on Curse.com either) is idiotic.
I still use several addons that have been working without any code changes since Wrath, and at least one that's been unchanged since the Burning Crusade, FFS. An addon that's feature-complete and has no outstanding bugs to be fixed simply does not need to have a new release every 3 months.
Go to your project page -> Edit project -> Scroll down to the bottom -> Set "Development stage" to "Mature" -> Update. Now you'll only be spammed by "OMG UR ADDON MUST BE ABANDONED!!!!!11111!!" warnings when a new expansion comes out.
What is wrong with mature addons? The mass majority of mine are this way. Hell, I have addons that have not been touched since wow 2.0 and work just fine to this day. Those addons are most certainly not abandoned and work perfectly fine, they do not warrant touching the files every 90 days.
Please keep the mature status around, it is very valid. I'll gladly verify that my "mature" addons still work every major patch if you guys drop this crazypants 90 day timer and leave the "mature" state in.
I mean, hell, sometimes wow doesn't even get a patch every 90 days!
Unless I'm mistaken, the inactive/abandoned status was only applied to addons that hadn't received an update for the 90 days prior to patch 6.0.2 going live. I don't believe it's supposed to be recurring.
Unless I'm mistaken, the inactive/abandoned status was only applied to addons that hadn't received an update for the 90 days prior to patch 6.0.2 going live. I don't believe it's supposed to be recurring.
Yes, it's not every 90 days, it's related to patch version numbers.
It's supposed to be 90 days from a new version. Not every 90 days.
Do you mean "new version hits + 90 days" or "if new version and last update < 90 days"? Because the latter seems to be true.
What's wrong with taking the interface version that the WoW client uses to recognize out-dated addons? This at least requires an TOC update and thus a status change is justified. In this case, there is also no need to wait 90 days.
Unless I'm mistaken, the inactive/abandoned status was only applied to addons that hadn't received an update for the 90 days prior to patch 6.0.2 going live. I don't believe it's supposed to be recurring.
When patch 6.0.2 went live all addons were marked as "Abandoned" -- not just Inactive, but actually Abandoned -- less than 24 hours later, regardless of when they'd last been updated. At that point I'd already updated several of my addons for the patch -- they were also flagged as "Abandoned", and I had to manually edit my project to change the status back to "Release".
Outside of expansion releases, addons are automatically marked as "Inactive" if no new version is uploaded within 90 days of the previous version, even if there have been no WoW patches in that time. This is unnecessary and annoying, and should not happen, and is why I (and others) are setting the project status on our addons to "Mature", because projects marked as "Mature" are never automatically changed to "Inactive".
Apparently the "Mature" status is intended only for libraries, but I fail to see why any such distinction should be made. If my addon doesn't require an update for 90 days, why should I be forced to waste my time changing a dropdown from "Inactive" to "Release" over and over again?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
At present it's been less than 24 hours since the patch went live, and already you flagged EVERY SINGLE ONE of my several dozen addons as abandoned. F*** off. Seriously.
In the email I received in the title it says inactive but afterwards the wording changes to abandoned
The addons are still downloadable on Curse ... so they won't be removed from Curse just yet I hope?
If not, the whole thing seems like a major problem for those of us who maintain addons where the original authors/managers aren't really around anymore. (Although maybe inactive doesn't really mean much, since it doesn't seem to be stopping it from being available on Curse...)
If the original author left, and noone has officially managed to take the project over (ie. by getting permission from the author and getting manager status on the project), it does kinda mean that the project at least is somewhat inactive.
I think the inactive pass was too aggressive this time, as it usually only does its thing after months of inactivity and no current version, and not one day after the expansion release, but what can you do, just update them and set them back to release.
And yeah, the inactive thing was kinda crazy. In no way were a lot of these addons inactive.
Well, auto-marking my addon as inactive/abandoned if I don't post an update for 90 days is unacceptable, so I'm going to continue marking my mature addons as "Mature". There's just no logical reason to force me to waste everyone's time (especially my own) by posting fake updates for 40+ addons every 90 days. :mad:
Use the microscopic "report" icon in the bottom right corner of the project page to ask a moderator to bump you up to Project Manager. If you're already listed on the project and actively maintaining it, and the manager is AWOL, there's no reason not to promote you.
And Torhal is going to be unflagging them again.. He likes that part of his job! :D
As long as they have a file thats for the current version of WoW, they shouldn't get flagged. None of mine did, until the day 6.0 was set as the primary WoW version (where the over aggressive comes in)
Example: http://www.wowace.com/addons/incognito/
Loaded w/o complaints by the WoW client, so no need to update the addon, not even for a TOC update.
I still use several addons that have been working without any code changes since Wrath, and at least one that's been unchanged since the Burning Crusade, FFS. An addon that's feature-complete and has no outstanding bugs to be fixed simply does not need to have a new release every 3 months.
Go to your project page -> Edit project -> Scroll down to the bottom -> Set "Development stage" to "Mature" -> Update. Now you'll only be spammed by "OMG UR ADDON MUST BE ABANDONED!!!!!11111!!" warnings when a new expansion comes out.
Please keep the mature status around, it is very valid. I'll gladly verify that my "mature" addons still work every major patch if you guys drop this crazypants 90 day timer and leave the "mature" state in.
I mean, hell, sometimes wow doesn't even get a patch every 90 days!
Yes, it's not every 90 days, it's related to patch version numbers.
Do you mean "new version hits + 90 days" or "if new version and last update < 90 days"? Because the latter seems to be true.
What's wrong with taking the interface version that the WoW client uses to recognize out-dated addons? This at least requires an TOC update and thus a status change is justified. In this case, there is also no need to wait 90 days.
When patch 6.0.2 went live all addons were marked as "Abandoned" -- not just Inactive, but actually Abandoned -- less than 24 hours later, regardless of when they'd last been updated. At that point I'd already updated several of my addons for the patch -- they were also flagged as "Abandoned", and I had to manually edit my project to change the status back to "Release".
Outside of expansion releases, addons are automatically marked as "Inactive" if no new version is uploaded within 90 days of the previous version, even if there have been no WoW patches in that time. This is unnecessary and annoying, and should not happen, and is why I (and others) are setting the project status on our addons to "Mature", because projects marked as "Mature" are never automatically changed to "Inactive".
Apparently the "Mature" status is intended only for libraries, but I fail to see why any such distinction should be made. If my addon doesn't require an update for 90 days, why should I be forced to waste my time changing a dropdown from "Inactive" to "Release" over and over again?