is there any updater out there that can update from http://www.wowace.com/projects/ ? because I can find a lot more up2date files there than on curse.com
The only way to update from project pages is to manually download the .zip under Files or use SVN, Git, etc, to get the files directly. Either way is manual and unless you're an addon developer or helpful tester, there's no real benefit of getting the files from WoWAce over Curse/CurseForge.
well that depends on what's your definition of a tester, I am posting error messages/suggestions for improvements as far as it is possible for me, but I am not that kind of person who is willing to excessive test the addons I am using, besides I'm not keen in coding ;)
this question just came into my mind because I was waiting for an addon to update on curse for over a week, because there was an annoying bug. today I downloaded the newest version from wowace and it was fixed.
let's say it like this: As I told you above, I want to help as far as it is possible for me and I would accept using "unstable" revisions if they can fix my issues. I mean it was never really a problem to use the revisions from the bleeding edge of development, I personally could live without having to wait for the super stable release versions. This wasn't the case while the old files.wowace existed, we all updated the addons from their current state of develepment, at least I think so :) .
This was no effort to start assaulting wowace's bandwith again, but perhaps the existance of such an updater would lead to this.
Kaelten has specifically addressed this. The Curse updater will include support for alphas "within a couple weeks". This will enable the updater to get the very latest commit, no matter how buggy it may be. I highly don't recommend doing this unless you're specifically testing the add-on, because a lot of authors including myself are now committing buggy code more frequently, since we know millions of people will not necessarily be downloading those commits instantaneously.
... I would accept using "unstable" revisions if they can fix my issues. I mean it was never really a problem to use the revisions from the bleeding edge of development, I personally could live without having to wait for the super stable release versions. This wasn't the case while the old files.wowace existed, we all updated the addons from their current state of develepment, at least I think so.
Eh well this is more a problem of the author not the site.. If the author fixes something in a commit and they arn't really developing it that night with several commits, they should push a new beta or release.
Eh well this is more a problem of the author not the site.. If the author fixes something in a commit and they arn't really developing it that night with several commits, they should push a new beta or release.
So bug the author to use the site correctly :P
On the other hand, there is no need to release an update every night. Some authors like to do "weekly releases" where every week they will release a new version if there is any update to it, unless a fix is critical to the addon's performance. Right now, Omen3 is following this approach, I don't need 10 million downloads just because I push a small commit every night, instead of 10 commits every 10 nights.
Also right now some of those 'fixes' might not be from the project author but other developers just helping out. Nobody but those listed as authors of the project (and those of us with some site moderation access) should be posting 'releases' out to curse. Thats why you may be waiting for a while for fixes to some addons to be updated on curse.
Nobody but those listed as authors of the project (and those of us with some site moderation access) should be posting 'releases' out to curse.
I am not even sure non-authors (beside mods) could still create beta/release packages. Didn't ckknight change that ? Something like "non-author tags are never marked as beta or release."
I am not even sure non-authors (beside mods) could still create beta/release packages. Didn't ckknight change that ? Something like "non-author tags are never marked as beta or release."
It might be an option, unless it recently changed. I've been able to push FuBar2Broker releases with andreasg's permission, even though he is the only author.
On the other hand, I've also seen addons like EnhancedColourPicker where the WowAce project page won't even package alphas, so community checkins are never visible unless you go directly to the SVN.
Kaelten has specifically addressed this. The Curse updater will include support for alphas "within a couple weeks". This will enable the updater to get the very latest commit, no matter how buggy it may be. I highly don't recommend doing this unless you're specifically testing the add-on, because a lot of authors including myself are now committing buggy code more frequently, since we know millions of people will not necessarily be downloading those commits instantaneously.
I sometimes commit alpha that i know is way buggy. i do that so i can work on it from multiple stations when i have time.
i don't think the updater should allow alpha at all.
I sometimes commit alpha that i know is way buggy. i do that so i can work on it from multiple stations when i have time.
i don't think the updater should allow alpha at all.
Users who enable alpha support on the Curse Client should only be doing so if they want to help with the testing stages. If they do so otherwise, it's their fault when their shit breaks.
Users who enable alpha support on the Curse Client should only be doing so if they want to help with the testing stages. If they do so otherwise, it's their fault when their shit breaks.
I second that. Plus the Curse Client is going to tell them "you're going to install potentially broken code" (it is already doing so for betas). If they come to the site and make a good report to help fix the issue when they find one, that's fine. (And remember that quality can be chosen globally and per addon.)
is there any updater out there that can update from http://www.wowace.com/projects/ ? because I can find a lot more up2date files there than on curse.com
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Project AuthorUp-to-date does NOT mean release-quality, stable, or even in working condition. Use Curse, period.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorThen, by all means, download from the projects pages. The OP stating "up2date", however, told me he isn't a tester and just wants a fix.
this question just came into my mind because I was waiting for an addon to update on curse for over a week, because there was an annoying bug. today I downloaded the newest version from wowace and it was fixed.
let's say it like this: As I told you above, I want to help as far as it is possible for me and I would accept using "unstable" revisions if they can fix my issues. I mean it was never really a problem to use the revisions from the bleeding edge of development, I personally could live without having to wait for the super stable release versions. This wasn't the case while the old files.wowace existed, we all updated the addons from their current state of develepment, at least I think so :) .
This was no effort to start assaulting wowace's bandwith again, but perhaps the existance of such an updater would lead to this.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumEh well this is more a problem of the author not the site.. If the author fixes something in a commit and they arn't really developing it that night with several commits, they should push a new beta or release.
So bug the author to use the site correctly :P
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOn the other hand, there is no need to release an update every night. Some authors like to do "weekly releases" where every week they will release a new version if there is any update to it, unless a fix is critical to the addon's performance. Right now, Omen3 is following this approach, I don't need 10 million downloads just because I push a small commit every night, instead of 10 commits every 10 nights.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI am not even sure non-authors (beside mods) could still create beta/release packages. Didn't ckknight change that ? Something like "non-author tags are never marked as beta or release."
It might be an option, unless it recently changed. I've been able to push FuBar2Broker releases with andreasg's permission, even though he is the only author.
On the other hand, I've also seen addons like EnhancedColourPicker where the WowAce project page won't even package alphas, so community checkins are never visible unless you go directly to the SVN.
You will create a new method of getting the latest and greatest addons.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIf they all go SVN, we still have Hg and Git to hide behind. :p
I sometimes commit alpha that i know is way buggy. i do that so i can work on it from multiple stations when i have time.
i don't think the updater should allow alpha at all.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorUsers who enable alpha support on the Curse Client should only be doing so if they want to help with the testing stages. If they do so otherwise, it's their fault when their shit breaks.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI second that. Plus the Curse Client is going to tell them "you're going to install potentially broken code" (it is already doing so for betas). If they come to the site and make a good report to help fix the issue when they find one, that's fine. (And remember that quality can be chosen globally and per addon.)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThough I really don't have much faith that the average user would read that. ;)