I've managed to get my addons committed to the SVN after a bit of hassle working out locations of new libraries. Its been a learning curve for sure but it looks like this will be a smoother method of working after things settle down.
My concern is that doing an SVN commit seems to have updated the date stamp on my curse.com project page even though there was no new release version. This behaviour may cause users to think there is a new version to download when none exists. I suspect also that the updater might think the project had a new release?
I think this is a BIG mistake, a lot of users will be put off by the current state of the Curse updater when they have been used to the WAU. In time no doubt these issues will go away, however for now I suspect a LOT of people will manually update and rely on their favourites showing a project has been updated. If a background commit of a non-release tagged version updates the project timestamp on Curse.com (I could understand Curseforge.com timestamp update) then a whole lot of people are going to get even more confused. As they will think there is something new to download when there isn't.
Ah, so that's why I've been seeing phantom updates to my favorites on curse.com for the past few months? Yeah, that's a serious issue. Honestly, the "last updated" timestamp should go off of the timestamp of the most recently available file.