Hello again. I am looking for advice from @doktormo … I am willing to continue to maintain the Blink Binding but I don’t want to overstep my role. I have forked your repo and you’ve read this thread so you know this…. But in order to “publish” to the add-on marketplace, I would likely create a New Topic with similar wording, and post my Jar, and a link to my GitHub repo, as instructed here.
On the surface, this looks like I’m stepping all over you and your original blink 0.1 (and 0.1.1) release jars. I don’t want to be rude like that. Mostly I just don’t understand what I should do at this point. Of course, due to changes by Blink, none of the previous releases function at all, so it’s not like I could break anything technically–I’m just worried about procedural and emotional damage!
Also I have a few minor questions for you like:
- did you build the 0.1 and 0.1.1 jars manually, and then upload them on the separate
blinkreleasebranch so they appear in the marketplace? (They weren’t BUILT by GitHub somehow, right?) - Why didn’t your later changes get built and posted the same way? Why use the google drive? (No judgment, just looking for advice)
- If I were to publish the same way you did, what happens to your 0.1.1 release in the marketplace? Would it co-exist along with my “5.2” release?
- How does the “older” 0.1.1 release in the marketplace get removed or replaced?
- How does version control work? How do marketplace users see the “latest” release of a community contributed add on? Do I modify my “new topic” post when I have a subsequent release, or do I create another “new topic” for my second release?
Actually I’m going to tag a few other people in here in case they could chime in with the proper procedure. I just don’t want to do it wrong and make unnecessary waves! @ysc and @lsiepel might be able to help guide me! (maybe I should re-post this marketplace version control question in the marketplace forum)