I'm hoping in nUI's case that the same addon can be used in both Classic and Current servers using the Number of Expansions constant that can be used to test whether it is on a Classic server or Current. Then apply the code blocks that are appropriate. Then it would be the case of simply uploading as normal. Hopefully
Originally Posted by MooreaTv
What is the eventual branching/tagging strategy here ?
ie as an addon author (and likewise for users, ui wise) how do I indicate 2 versions for 1 addon
I hope we won't just clone all addons with a random classic prefix/suffix - it'll be a nightmare
What I propose is support for git branches or multiple top tags (If I manage to write an addon that does work with same code for both, than I can tag a single release with both the classic and bfa versions, somehow)
Any other ideas/thoughts ?
ps: I asked the same here https://authors.curseforge.com/forum...branching-tags
ps: also waiting on full beta but was able to start to test on stress test finally, unfortunately there are only a few hours left (and I also had 2 PTRs but got support to delete one of them, possibly too late... I hope it can be manually fixed by someone somehow)
|