I'm just looking for opinions. here. My addon is designed to be universal, meaning that it works with all versions of Retail and Classic WoW. The addon determines the client, and only displays content appropriate to that client. Since my addon contains raid/boss information, it will be fairly common for updates that will only affect Retail. In these cases, Classic users won't notice any changes, since the addon doesn't show Retail information to them. Okay, here's my question:
What are your thoughts about updates? Should I push "retail only" updates to all three clients, just to keep the version numbers consistent, or should I push those updates only to retail, meaning that Classic users will skip versions or think that they're no longer getting updates? I like the idea of someone being able to simply copy/paste the addon folder to any other version, and it would just work (although, thanks to CurseForge not understanding multi-version .toc files, that isn't entirely true), but I don't want people to think I'm just trying to pad my dl numbers, by having people dl updates with nothing new for their client.
More like "Post that update to all clients because the bigwigs packager doesn't care about that"
but there probably is a way to make a github workflow that only pushes uploads for a specific flavor when a tag has a certain name, e.g. 1.0.1-classiconly
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm just looking for opinions. here. My addon is designed to be universal, meaning that it works with all versions of Retail and Classic WoW. The addon determines the client, and only displays content appropriate to that client. Since my addon contains raid/boss information, it will be fairly common for updates that will only affect Retail. In these cases, Classic users won't notice any changes, since the addon doesn't show Retail information to them. Okay, here's my question:
What are your thoughts about updates? Should I push "retail only" updates to all three clients, just to keep the version numbers consistent, or should I push those updates only to retail, meaning that Classic users will skip versions or think that they're no longer getting updates? I like the idea of someone being able to simply copy/paste the addon folder to any other version, and it would just work (although, thanks to CurseForge not understanding multi-version .toc files, that isn't entirely true), but I don't want people to think I'm just trying to pad my dl numbers, by having people dl updates with nothing new for their client.
Thoughts?
More like "Post that update to all clients because the bigwigs packager doesn't care about that"
but there probably is a way to make a github workflow that only pushes uploads for a specific flavor when a tag has a certain name, e.g. 1.0.1-classiconly